Versions Compared

Old Version 6

changes.mady.by.user Derya Özdemir

Saved on

compared with

New Version Current

changes.mady.by.user Derya Özdemir

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Auibutton
titleServer
typesubtle
urlEI4J:Execution Logs
Auibutton
titleCloud
typestandard
urlExecution Logs

List of Execution Logs

Each webhook triggers

Button handy
blankfalse
color#0052CC
nameCloud
linkhttps://appfire.atlassian.net/wiki/spaces/EIFJC/pages/10125437/Installation
width84
Button handy
blankfalse
color#EBECF0
nameOn-Prem
linkhttps://appfire.atlassian.net/wiki/spaces/EI4J/pages/11206868/Installation
width85

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#F4F5F7

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

logged. The following screen shows the initial view of the Execution Logs.

Image Removed

Successful Process

Each

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.

    Image Added

🎯 Index

Table of Contents
minLevel3
maxLevel6
outlinefalse
typelist
printablefalse

Successful Process

In the Execution Logs, each successful action execution is displayed with

the maximum detailed information, for example:

Image Removed

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.

Image Added

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

Waiting to

retry 

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

was

failed

on

during the previous attempt

if the retry is configured.Image Removed

. 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.

Image Added

Event Data

Each webhook event

sends

generates a JSON object that is sent to

the

Easy Integrations. The

contents

structure and

shape

content of

the

this event data

depends

depend on the type of event

type

. For

example, for the issue-related events, issue data is included

instance, events related to issues will contain relevant issue data.

Action execution data

Action data can be viewed

For more in-depth information about a specific action execution, you can access detailed logs by clicking on the action name

on

within the "Action execution history" table in the Execution Logs. The following

information is logged

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

Example screenshots

Click on the image to enlarge.

Image RemovedImage Removed

Console logs of user scripts

Each script console logs, for example,

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

Image Added
Image Added

Console Logs of User Scripts

Any console logs generated by user scripts, such as "console.log('test'),

 are logged

" are also captured and can be viewed

on the master execution logs menu as

within the Execution Logs. You can access these logs under the "Console logs of user scripts" section.

Image Removed

These logs are useful for debugging and monitoring the behavior of custom scripts in your integration workflows.

Image Added