Not getting the Adobe IO runtime action logs

It looks like you’re not able to view logs for your Adobe I/O runtime actions after triggering them from Postman. Here's what you might be missing:

1. Check Log Level Configuration

• Ensure your actions are configured to log at an appropriate level (e.g., console.log() statements should be visible if correctly set).
• If you're using Adobe I/O runtime (OpenWhisk), logs should show up in the activation logs. Ensure that your action is not silently failing before reaching the console.log() statements.

2. Log Retrieval Command

• After running wsk activation list, use the wsk activation logs command to retrieve logs for a specific activation. Example: wsk activation logs <activation-id>
  If no logs appear, check if the activation ID from the wsk activation list is correct.

3. Activate Your Action

• Make sure that your action has been triggered properly and that it ran successfully. You can trigger the action by hitting the API endpoint or manually through:wsk action invoke <action-name> --blocking --result

  4. Check if Logs Are Enabled

  • Logs might not be displayed if they're not configured or if the action was executed asynchronously.
  • Ensure that you are using the correct environment for viewing logs and that the console output is properly captured.

  5. Runtime Environment Logs

  • Logs for actions are sometimes stored in the Adobe I/O Runtime environment logs. You might need to check specific runtime settings or permissions to view them properly.

  6. Permissions and Access

  • Double-check that your credentials and access permissions are properly set up to view the logs from the Adobe I/O Runtime.

  Summary:

  • Use wsk activation logs <activation-id> to get detailed logs.
  • Ensure actions are correctly triggered and the logs are enabled.
  • Verify your environment, credentials, and API call configurations.