JIRA is an issue and project tracking system for software teams. This integration allows you to create tickets from triggered alerts in Datadog, and update existing tickets with new information as it arises. Additionally, you can see JIRA ticket creations as events within Datadog to overlay with all of your metrics.
Navigate to your Jira account
Go to settings (Gear icon) –> Applications
Under “Integrations” in left menu, Select Application Links
https://app.datadoghq.com/ as the URL to link –> press “Create new link” (Note: You may see a warning “No response was received from the URL you entered.” You can ignore this and press Continue.)
Fill in Application Name with any name (used simply for identification)
Leave Generic Application Selected
Check “Create Incoming Link”
Copy and Paste the Consumer Key, Consumer Name, and Public Key from the Jira tile
Navigate back to the Jira Tile
Copy and paste the URL of your Jira account into the tile from http… to .net i.e https://some-account.atlassian.net
Check to see if you can select a Project when creating a new Ticket Type. If this dropdown is empty, it means the integration is not properly installed (or your Jira account has no Projects!)
The JIRA integration does not include any metric at this time.
All JIRA ticket creations appear as events within Datadog
The JIRA integration does not include any service check at this time.
Need help? Contact Datadog Support.
After installing the JIRA integration, you can create custom tickets types that can be created within Datadog.
Raw values as well as variables from the alert event can be used to fill in these 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_alert_monitor)|
|$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: https://url.to.snpashot.com/)|
|$LINK||Url of the event (ex: https://app.datadoghq.com/event/jump_to?event_id=123456)|
|$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)|
To automatically have JIRA tickets created within Datadog alerts, use the @jira-projectname-issuetype command within the “Say what’s happening” section of the new monitor creation process.
A new ticket will be created when this alert is triggered.
The @jira-update command can be used to update existing tickets. This command will add a comment to the JIRA ticket with the text followed by the @jira-update command.
TIP – It might be useful to use the @jira command within an #is_alert or #is_warning variable!