Sleuth Documentation
HomeBlogSupportSign up
  • Getting started
  • Navigating Sleuth
  • DORA metrics
    • Deploy frequency
    • Change lead time
    • Change failure rate
    • MTTR
    • Interpreting Metrics in Sleuth
  • Deployment tracking
    • Organization
      • Labels
      • Trends
      • Compare
      • Search
      • Status
    • Projects
      • Issue trackers
    • Environments
    • Code deployments
      • Creating a deployment
      • How to register a deploy
      • Rollbacks
      • Automatic tagging
      • Deployment locking
      • Environment drift
      • Move code deployments
      • Search everything
    • Feature flags
    • Manual changes
    • Deploys
    • Teams
  • Work in Progress
  • Goals
  • Sleuth Automations
    • Automations Marketplace
      • Installing Automations
        • Installing PR "Update" Automations
      • Editing and uninstalling Automations
      • Smart suggestions
      • Understanding efficacy
    • Custom Automations
      • Automations Cookbook
      • Webhook Actions
      • Trigger Build Actions
        • Bitbucket Pipelines
        • CircleCI
        • Github Actions
        • Jenkins
  • Slack & Email Notifications
  • Auto-verify deploys
    • Anomaly detection
    • Error impact
    • Metric impact
  • Ignoring pull requests
  • Slack mission control
    • Approvals
    • Project notifications
    • Personal notifications
    • Search Sleuth in Slack
    • Project/Deployment history
    • Developer standup
  • Sleuth API
    • Deploy Registration
    • Deploy import
    • Manual Change
    • Custom Incident Impact Registration
    • Custom Metric Impact Registration
    • Deprecation information
    • GraphQL Queries
    • GraphQL Mutations
    • Query batching
  • Integrations
    • About Integrations...
    • Code integrations (read-only)
      • Azure DevOps
      • Bitbucket
      • GitHub
      • GitLab
      • Custom Git
      • Terraform Cloud
    • Code integrations (write)
    • Feature flag integrations
      • LaunchDarkly
    • Impact integrations
      • Error trackers
        • Bugsnag
        • Honeybadger
        • Rollbar
        • Sentry
      • Metric trackers
        • AppDynamics
        • AWS CloudWatch
        • Custom
        • Datadog
        • Jira metrics (Cloud / Data Center)
        • NewRelic
        • SignalFx
      • Incident tracker integrations
        • Blameless
        • PagerDuty
        • Datadog Monitors
        • Statuspage
        • Opsgenie
        • Jira (Cloud/Data Center)
        • FireHydrant
        • Rootly
        • ServiceNow
        • Custom
          • Grafana OnCall
      • CI/CD builds
        • Azure Pipelines
        • Bitbucket Pipelines
        • Buildkite
        • CircleCI
        • GitHub Actions
        • GitLab CI/CD Pipelines
        • Jenkins
    • Sleuth DORA App for Slack
    • Microsoft Teams integration
    • CI/CD integrations
      • Azure Pipelines
      • Bitbucket Pipelines
      • Buildkite
      • CircleCI
      • Github Actions
      • GitLab CI/CD Pipelines
      • Jenkins
    • Issue tracker integrations
      • Jira Cloud
      • Jira Data Center
      • Linear
      • Shortcut
    • Fixing broken integrations
  • Pulse
    • Welcome to Pulse docs
    • Quick Start setup guide
    • Beginner tutorials
      • 1. How to create a Teamspace
      • 2. How to create a Review
      • 3. How to create a Survey
  • Features
    • Reviews
      • Review workflow
      • Review templates
      • Widgets and Sections
        • Widget type
      • Review settings
    • Surveys
      • Survey Workflow
    • Teamspaces
    • Inbox
    • AI assistant
    • General settings
      • Users and Teams
      • Investment mix
  • Settings
    • Organization settings
      • Details
      • Authentication
        • SAML 2.0 Setup
          • Okta Configuration
          • Azure AD Configuration
          • PingIdentity Configuration
      • Access Tokens
      • Members
      • Team Settings
      • Billing
    • Project settings
      • Details
      • Slack settings
      • Environment settings
      • Code deployment settings
      • Feature flag settings
      • Impact settings
    • Account settings
      • Account settings
      • Notifications settings
      • Identities settings
    • Role Based Access Control
  • Resources
    • FAQ
    • Sleuth TV
    • Purchasing
    • About Sleuth...
Powered by GitBook
On this page
  • About the integration
  • Setting up the integration
  • Configuring the integration
  • Using the integration
  • Removing the integration

Was this helpful?

  1. Integrations
  2. Impact integrations
  3. Incident tracker integrations

Custom

PreviousServiceNowNextGrafana OnCall

Last updated 3 months ago

Was this helpful?

About the integration

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.

Setting up the integration

A Custom Incident Impact Source is always available within your Sleuth project(s). No additional configuration is needed. See '' below for details on how to use a Custom Incident Impact Source.

Configuring the integration

  • 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.

Using the integration

The webhook sent to Sleuth must contain the mandatory type parameter, the value can be:

  • triggered

  • resolved

  • reopened

There are also several optional parameters, such as:

  • id: The unique incident identifier in your system

  • date: The ISO 8601 date the event occurred, defaults to the current time

  • title: The human readable title of the incident

  • url: URL to incident in your external system

Removing the integration

To remove the custom incident source

  1. Click on your Project Settings --> Impact

  2. Find the Impact Source you'd like to remove, click the pencil icon to display options, and then click Delete.

To access the detailed instruction on how to use the Impact Source at any time, navigate to the Impact Source, click the icon in the top-right corner, and click Show register details.

⚙️
Configuring the integration
You can also always come back to this page by navigating to the Impact Source, clicking the gearwheel in the top right, and selecting Show register details.