Execution Logs

Owned by Tolga Tunca
Last updated: Oct 25, 2023 by Derya Özdemir
3 min read

This page is about Easy Integrations for Jira Cloud. Using Jira On-Prem? Click the On-Prem button above.

Execution Logs provide valuable insights into the operation of webhook-triggered actions and listeners within the Easy Integrations platform. They help track the execution status, detailed information on each action, event data, and even user script console logs. This documentation outlines the key elements and features of Execution Logs for effective monitoring and troubleshooting.

Execution Log Viewer

When a webhook is triggered, it initiates one or more matching Easy Integrations listeners, and each listener's execution is recorded within the Execution Logs. To access the logs, follow these steps:

  1. Navigate to Jira's top menu, and click Apps.

  2. Select Manage your apps.

  3. In the sidebar, locate and click Easy Integrations configuration.

  4. Select Execution Logs from the app’s top menu.

Successful Process

In the Execution Logs, each successful action execution is displayed with maximum detail, providing valuable information for analysis. Key information recorded for a successful action execution includes actions status, URL, reference ID, method, request time, response status code, duration, request header, request body, and more.

This detailed information can help you verify the successful execution of your actions and identify any potential issues or areas for improvement.

Failed Process, but Waiting to Retry

In the case of a failed action execution, Easy Integrations will automatically schedule a retry based on your configured settings. The process will continue from where it failed during the previous attempt. This retry mechanism ensures that no critical actions are lost due to transient issues. The specific details of the failed action execution will also be available in the Execution Logs.

Event Data

Each webhook event generates a JSON object that is sent to Easy Integrations. The structure and content of this event data depend on the type of event. For instance, events related to issues will contain relevant issue data.

Action execution data

For more in-depth information about a specific action execution, you can access detailed logs by clicking on the action name within the "Action execution history" table in the Execution Logs. The following data is provided for each action execution:

  • Action status

  • Reference ID

  • URL

  • Method

  • Request time

  • Response status code

  • Duration

  • Request header

  • Request body

  • Response headers

  • Response body

These logs are crucial for diagnosing and resolving any issues that may arise during action execution. Check out the examples below:

Console Logs of User Scripts

Any console logs generated by user scripts, such as "console.log('test')," are also captured and can be viewed within the Execution Logs. You can access these logs under the "Console logs of user scripts" section. These logs are useful for debugging and monitoring the behavior of custom scripts in your integration workflows.

Â