Comment on page
Jira metrics (Cloud / Data Center)
Jira is an issue tracking tool that integrates with Sleuth in support of various use cases (as a general deployment tracking issue integration, as an incident impact source, etc.). This article is specific to using Jira as a metric impact source, which allows you to define a JQL query that returns a count of matching Jira issues and compare those against user-defined environment health thresholds. A common example here would be retuning the number of currently open bug tickets in Jira as an indicator of health.
Once the Jira integration has been enabled for your Sleuth organization, perform the following steps to configure it as a Metric impact source.
- Navigate to the Sleuth Project for which you'd like to add Jira as a metric impact source.
- From the Project's left-hand menu, click Impact sources and select + Add impact source
- In the field titled How do you track change failure?, select Metrics
- If the Jira integration has been properly enabled for your Sleuth organization, the integration tile will show "enabled".
- Click the tile to configure the Jira metric impact source.
- In the following screen, give your metric impact source a name, specify which environment it's for, and enter a JQL query that returns a count.
- Optionally, under Advanced settings, you can specify a threshold under which the count returned by the metric impact source will be considered healthy.
- Test the connection to verify it's retuning the expected counts, and click Save.
- That's it! Sleuth will now start verifying your deploys' health by tracking the values from your Jira metric. To view the new metric, simply choose your new impact source from the Project's left-hand navigation.
- 1.Open the metric impact source from the Project's left-hand navigation menu.
- 2.Click the cog in the upper-left-hand side of the screen and click Delete