Webhook execution logs

Webhook execution logs make Email This Issue for Jira administrators able to monitor which webhooks have been called upon which incidents, and whether the associated HTTPs requests have been dispatched successfully.

To see Webhook execution logs, go to the Administration tab, and choose Webhook Execution Logs under WEBHOOKS.

If webhooks are called successfully the admins or all other addressed parties are informed about the source incidents through the preferred channel for which the webhook was configured.

If the webhook itself does not work properly, the incidents won't reach the receiving system, and won't be reported there either. To learn about such an issue, check the logs of webhook executions. Issues with webhook call dispatching cannot be reported in the style of push notifications, they must be actively checked (polled) periodically.

On the listing page of webhook execution logs items are ordered by their time of execution, in a descending order starting with the latest items. There are 100 items per page. Assuming that only the most recent logs may refer to relevant, current issues, execution logs can neither be filtered, nor deleted. They are automatically purged after 90 days.

Each log entry contains the most essential details about the incident that triggered the webhook call, and some additional information about the execution. especially in the event of failure in order to make troubleshooting possible. As some fields may contain lengthy text (for example, error messages extended with stacktrace), these parts are displayed as collapsed by default, but they can be expanded individually if needed.

Note: When webhooks are called, all placeholders (velocity variables) are replaced by their current value. The substituted parameters applied in the request are shown in the execution log. Validate if templates are correct by sending a test notification and checking the log.

The following attributes are revealed in a log entry:

Last updated