Custom
Last updated
Last updated
Some teams track incidents using tools Sleuth doesn't have an out-of-the-box integration with yet or even outside of traditional Observability tools. Custom Incident Impact Sources allow you to submit values collected by these tools to Sleuth and get your Failure Rate and MTTR values.
A Custom Incident Impact Source is always available within your Sleuth project(s). No additional configuration is needed. See 'Configuring the integration' below for details on how to use a Custom Incident Impact Source.
Navigate to the Project you want to add the Impact Source to.
Click Add in the top navigation bar and select Impact source from the list.
Select Incident management (recommended) from the How do you track change failure drop-down located towards the top of the page.
Choose Custom Incident - user provided from the selection of tiles/providers.
On the Configure impact source page, enter a name for your Impact Source (we recommend choosing a name that's descriptive, such as "Production incidents"), select the environment you want the collected incident data to apply for from the dropdown, and click Save.
Once the Impact Source is created, a window will pop up, providing instructions on how to use the Impact Source to register incident events.
That's it! Sleuth will now start monitoring incidents from your custom source. Head over to the Dashboard to start seeing your data in action in the project and deploy health graphs.
Click on your Project Settings --> Impact
Find the Impact Source you'd like to remove, click the pencil icon to display options, and then click Delete.
