# Error impact Error monitoring services help DevOps teams discover, triage, and prioritize the errors their applications produce in real-time. Error impacts are specific to a Sleuth [project](/sleuth-dora/modeling-your-deployments/projects.md) and [environment](/sleuth-dora/modeling-your-deployments/environment-support.md) and will be used to determine the health of that project/environment combination. Sleuth uses anomaly detection to determine your teams healthy range for the number of errors your application generates and will alert you and mark deploys as unhealthy when they are outside of your normal range. With each deploy, the error rate is sampled and correlated to the change that may have caused it. Sleuth supports the existing tools you already use such as [Sentry](/sleuth-dora/integrations-1/impact-sources/errors/sentry.md), [Rollbar](/sleuth-dora/integrations-1/impact-sources/errors/rollbar.md), [Bugsnag](/sleuth-dora/integrations-1/impact-sources/errors/bugsnag.md) and [Honeybadger](/sleuth-dora/integrations-1/impact-sources/errors/honeybadger.md). Error rates are displayed on the health graphs throughout the application. --- # Agent Instructions: 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: ``` GET https://help.sleuth.io/sleuth-dora/auto-verify-your-deploys/error-impact.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.