JIRA is an issue and project tracking system for software teams. This integration allows you to create issues from triggered alerts in Datadog, and update existing issues with new information as it arises. Additionally, JIRA issue creations are added as events within Datadog to overlay with your metrics.
Go to settings (gear icon) –> Products:
Under INTEGRATIONS in left menu, select Application links:
https://app.datadoghq.com/ as the URL and click Create new link. Note: You may see a warning “No response was received from the URL you entered.” Ignore this and press Continue.)
Fill in Application Name with any name (used for identification).
Leave Generic Application selected.
Check Create incoming link.
For the next box, obtain the Consumer Key, Consumer Name, and Public Key from the Datadog Jira integration tile.
Click the Setup OAuth1 button:
After installing the JIRA integration, create custom issue within Datadog.
Note: If you have the required field Severity (as shown above), Jira restricts the values allowed to:
Raw values and variables from the alert event can be used to fill in the issue fields. A full list of variables can be seen below:
|\$ID||ID of the event (ex: 1234567)|
|\$EVENT_TITLE||Title of the event (ex: [Triggered] [Memory Alert])|
|\$EVENT_MSG||Text of the event (ex: @webhook-url Sending to the webhook)|
|\$EVENT_TYPE||Type of the event _(ex: metric_alertmonitor)|
|\$LAST_UPDATED||Date when the event was last updated|
|\$DATE||Date (epoch) where the event happened (ex: 1406662672000)|
|\$AGGREG_KEY||ID to aggregate events belonging together (ex: 9bd4ac313a4d1e8fae2482df7b77628)|
|\$ORG_ID||ID of your organization (ex: 11023)|
|\$ORG_NAME||Name of your organization (ex: Datadog)|
|\$USER||User posting the event that triggered the webhook (ex: rudy)|
|\$SNAPSHOT||Url of the image if the event contains a snapshot (ex: |
|\$LINK||Url of the event (ex: |
|\$PRIORITY||Priority of the event (ex: normal)|
|\$TAGS||Comma-separated list of the event tags (ex: monitor, name:myService, role:computing-node)|
|\$TEXT_ONLY_MSG||Text of the event without markdown formatting|
|\$ALERT_ID||ID of alert (ex: 1234)|
|\$ALERT_METRIC||Name of the metric if it’s an alert (ex: system.load.1)|
|\$ALERT_QUERY||Query of the monitor that triggered the webhook|
|\$ALERT_STATUS||Summary of the alert status (ex: system.load.1 over host:my-host was > 0 at least once during the last 1m)|
|\$ALERT_TRANSITION||Type of alert notification (ex: Triggered)|
|\$HOSTNAME||The hostname of the server associated with the event (if there is one).|
|\$ALERT_CYCLE_KEY||ID to link events from the time an alert triggers until it resolves.|
|\$LOGS_SAMPLE||Logs sample from log monitor alerts.|
To automatically have JIRA issues created within Datadog alerts, use the
@jira-<PROJECT_NAME>-<ISSUE_TYPE> command within the “Say what’s happening” section of the new monitor creation process.
A new issue is created when this alert is triggered.
@jira-update command can be used to update existing issues. This command adds a comment to the JIRA issue with the text followed by the
TIP – You may find it helpful to use the
@jira command within an #is_alert or #is_warning variable.
The JIRA integration does not include any metrics.
All JIRA issue creations appear as events within Datadog.
The JIRA integration does not include any service checks.
Need help? Contact Datadog support.
On this Page