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
  • How does Sleuth handle security and protect my data?
  • How can I allow Sleuth to connect to resources behind my firewall?
  • Can I initialize a code deployment with more than 30 days worth of past deploys?
  • How do I register deploys if my deployment tool like ArgoCD or Harness only deploys artifacts and not Git SHAs?
  • Which browsers are officially supported?
  • How are environments represented in Sleuth?
  • How do I connect to my organization?
  • Can I get chat support?
  • How much does Sleuth cost?
  • Where can I find your Terms & Conditions?
  • What is your privacy policy?

Was this helpful?

  1. Resources

FAQ

PreviousRole Based Access ControlNextSleuth TV

Last updated 2 months ago

Was this helpful?

How does Sleuth handle security and protect my data?

Sleuth is SOC2 Type 2 certified. You can read about how Sleuth secures and manages your data in the .

Additionally, when you disconnect an integration, Sleuth purges all data, including any API keys/tokens, username/passwords, and any other information it needed to access your integration data.

How can I allow Sleuth to connect to resources behind my firewall?

Sleuth connects to many different systems to provide your full deployment picture. Some of these systems such as Github Enterprise, Jira and others may live behind a corporate firewall. Sleuth maintains three (for AZ redundancy) NAT gateways which all outbound traffic will originate from. To allow Sleuth to connect to your protected resources you will want to allow these IP addresses through your firewall:

  • 52.42.95.252

  • 44.225.94.110

  • 54.148.48.201

  • 35.162.250.51

  • 52.32.199.5

  • 35.81.173.156

Can I initialize a code deployment with more than 30 days worth of past deploys?

Yes, Sleuth allows you to manually import past data into a code deployment. Most teams don't need more than the 30 day baseline Sleuth provides out-of-the-box. However, if your team does you can follow these instructions for how to .

How do I register deploys if my deployment tool like ArgoCD or Harness only deploys artifacts and not Git SHAs?

Because Sleuth tracks Git SHAs (revisions or tags) as deploys, when your deployment system of choice is deploying an artifact instead of checking out a SHA and running the deploy there, it can be hard to know what to send to Sleuth as part of the deploy registration webhook.

The first solution to try is to find a way to pass the Git SHA along through to the deployment pipeline. That could be done by embedding the SHA into the version number or tag name, or as part of the artifact metadata. Then, in your deployment pipeline, extract that SHA and report it to Sleuth. If multiple repositories are involved, embed multiple SHAs and call multiple webhooks.

If that isn't an option, you may need to settle for an approximate deploy registration method. For example, have Sleuth track when a Git tag is created and treat that as a deploy. You could also have Sleuth track pushes to a specific branch, then add a fixed delay to approximate when the deploy would have likely been completed.

Which browsers are officially supported?

Sleuth officially supports up-to-date versions of all evergreen browsers (Chrome, Firefox, Edge and Opera). We also do our best to make sure everything works in latest Safari.

Browsers outside of the ones listed above represent less than 1% of all users and aren't officially supported. While we try to maintain a best-effort policy, we cannot guarantee everything will work.

How are environments represented in Sleuth?

How do I connect to my organization?

Someone on your team might have already created a Sleuth project and made some integrations. Instead of creating a new account and project from scratch, you can join their organization, which can be your team or your company.

If your email address domains match, you will automatically connect to the organization, which will give you access to all their projects and connected integrations.

Can I get chat support?

Yes! Sleuth has chat support. Look in the lower-right hand corner of your Dashboard and click on the chat icon to get instant chat support (available Monday thru Friday, 8 am to 5 pm PST).

How much does Sleuth cost?

Where can I find your Terms & Conditions?

What is your privacy policy?

Sleuth has full-featured support for environments, which are are created and managed at the level. You can have as many environments as needed to represent your project and its development states, with staging, testing, and production being common ones (you can name them anything you want).

Check out the to visualize Sleuth organization hierarchy.

Get detailed pricing and purchasing information on the page.

You can find Sleuth software Terms & Conditions .

Read the Sleuth Privacy Policy .

project
Sleuth Information Architecture
Purchasing
here
here
Sleuth Trust Center
Chat widget on the Dashboard
include as much past data as you'd like