Webhook Execution Logs make Email This Issue for Jira administrators possible to monitor, which webhooks have been called upon what incidents and whether the associated HTTPs requests have been dispatched successfully.
In a typical setting, if webhooks are called successfully, the admins - or all other addressed parties - are informed about the source incidents via the preferred channel, for which the webhook was configured. On the other hand, if the webhook itself does not work (properly), the incidents neither will reach nor will be reported in the receiving system, so the only way to learn about such an issue is to check the logs of webhook executions. Apparently, issues with dispatching the webhook calls cannot be reported in style of push notifications, they must be actively checked (polled) every now and then.
The listing page of webhook execution logs has a simple, pretty fixed structure: the logs are ordered by their time of execution, in a descending order (i.e. with the latest on top), 100 items per page.
Each log 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 some failure, in order to make the 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 upon need.