Not getting the Adobe IO runtime action logs

[Mahesh_Gunaje]

I have created the Adobe IO runtime project by creating necessary actions. I ran the command:

aio app build
aio app deploy

Got the Adobe IO runtime URL as well. Able to hit the API from postman. Got the response too.

Added console.log statements in my action files .Now, I want to check the logs details.

Here, I am facing the issue:

1: Not able to see my actions in the developer.adobe portal. Not an issue, since I can see the details if I run the command: aio runtime action list

2: After hitting the Adobe IO runtime api from postman, when I run the command: wsk activation list, I am not able to see any log files.

May i know, what I am missing?

cc @sarav_prakash  @mk_aem21  @arunpatidar 

[AMANATH_ULLAH · Accepted solution]

@Mahesh_Gunaje 

When Adobe IO action is hit, we get activation id in response header

Logs can be checked using the activation id. Please use the below command

wsk activation logs <activation ID>

[Mahesh_Gunaje]

Thanks a lot @AMANATH_ULLAH  for your quick help

Worked like a charm

[AmitVishwakarma]

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.

[Mahesh_Gunaje]

Thanks a lot @AmitVishwakarma  for your details response. Let me go through the steps.