Deploys are changes in your system, and anomalies occur as a result of those changes. Cased helps you track, understand, and respond to anomalies that occur after you deploy. Anomalies range from application errors to degraded performance to complete outages.

Anomalies are automatically detected and tracked

When you connect Cased to your existing tools, Cased will automatically detect anomalies and track them.

Anomalies are associated with deploys

When you deploy, Cased will automatically associate the anomaly with the deploy. This way, you can understand the impact of the deploy on your system.

Anomalies are easy to understand

Cased provides a simple interface to understand the impact of anomalies.

Anomalies can trigger incident response

Cased allows you to quickly create PagerDuty incidents directly from detected anomalies. This integration streamlines your incident response process, ensuring that your team can react promptly to critical issues. To create a PagerDuty incident from an anomaly:

  1. Navigate to the Anomalies dashboard in Cased.
  2. Locate the anomaly you want to escalate.
  3. Click on the “Create PagerDuty Incident” button associated with the anomaly.
  4. You can configure default PagerDuty service your team would like to use for incident creation at https://app.cased.com/connections/pagerduty.
ChangelogBranch deploys