> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/auto-verify-your-deploys/anomaly-detection.md).

# Anomaly detection

Sleuth applies anomaly detection algorithms to your impact data to do the heavy lifting required to determine what is normal and what is not.

All developers want to ship changes that are making systems better, not worse. However, in our modern environments it's often difficult to know:

* What metrics are important?
* Where do you find those metrics?
* And once found, what's normal and what's something to be worried about?

Trust Sleuth to let you know when your [metrics](/sleuth-dora/auto-verify-your-deploys/metric-impact.md) or [errors](/sleuth-dora/auto-verify-your-deploys/error-impact.md) are out of your normal range. We'll let you know within 2 minutes of your last deploy, right in Slack, where your developers already live.

![Sleuth performs complex statistical analysis to automatically determine when somethings abnormal](/files/-MSVOSo_AWXY6rxGFT3w)

The more data Sleuth collects the more we know what's normal for your team. For example, perhaps you're a team that keeps your errors empty by fixing every error that occurs. Or perhaps, which is often more realistic, you always have a "normal" number of errors that you've decided you're willing to accept. Sleuth's anomaly detection means your developers don't need to "magically know" which errors are normal and which are out of your norm.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.sleuth.io/sleuth-dora/auto-verify-your-deploys/anomaly-detection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.