Skip to main content
Skip table of contents

Monitor metrics and logs for relay

Jira administrators can monitor webhook requests whenever a configured webhook event is triggered by following the steps below:

Dashboard

The dashboard enables you to view insights that can help you assess the health of your webhook.

  1. Click on Webhook Relay at the left sidebar and then on the Dashboard tab.

  2. The Dashboard contains the following insights:

    GDFJ Dashboard elements 20241218.png

    1. Webhook call count: Number of times a webhook has been triggered and sent a request.

    2. Erroneous calls: Failed webhook requests.

    3. Mean latency: The time it takes for a webhook event to be processed and delivered.

    4. Webhook call count: The number of times the webhook has been executed.

    5. Webhook status code: The types of alerts triggered by a webhook. Statuses include:

      1. 200: Success. The request was processed successfully.

      2. 404: Not found. The requested resource could not be located.

      3. 405: Method not allowed. The HTTP method used is not supported for the requested resource.

Webhook logs

You can view the individual logs for each request at the Webhook Logs tab.

  1. Click on Webhook Relay at the left sidebar and then on the Webhook Logs tab.

  2. At the Webhook Logs tab, you can:

    1. Filter by time range.

    2. Filter by Actor (the person behind the intrusion).

    3. Download records from a time range. To do so, click Export as CSV, which creates a CSV format file in the default Downloads folder of the browser or a folder specified by the user.

    4. Order the data by categories, such as:

      1. Actor

      2. Timestamp

      3. Webhook event

      4. Webhook name

      5. Target URL

      6. Status code

      7. Status text

GDFJ webhook logs 20241218.png

Export as CSV will only export logs that are visible in the logs table. Only logs within a maximum range of two weeks prior can be retrieved and exported. For continuity of data, users are advised to maintain regular copies of record by exporting the logs as CSV file.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.