Coordinate response
Give the incident a case, and configure who should be paged and when.
Incident response
Give an incident an owner, a timeline and a place for its evidence. Your agent sets up the routing and opens the case. You check the case file on a read-only page.
Coordinate response with an incident and its recorded timeline.
Connect alerting, schedules, escalation and service ownership.
Follow attached Issues, service evidence and affected customers.
01The incident case
Your agent opens the incident and attaches the Issues and alerts that anchor it. The case file shows the state, the owner, the attached evidence and the response timeline.
02The evidence behind the alert
An alert brings attention to the problem. Traces, logs, Issues and customer-linked evidence help your team understand it. Your agent brings those findings into the response rather than leaving them between tools.
The workflow, connected
Connect operational routing with the evidence and communication around the response.
Your agent connects the alert or monitor to service ownership and the configured escalation path.
It assigns the incident, attaches the relevant signals and keeps the response timeline together.
Use status updates and response reports to carry the investigation into the follow-up.
The capabilities behind it
Preparation, investigation and communication belong to the same response workflow.
Give the incident a case, and configure who should be paged and when.
Watch services and external endpoints, then route failures through configured ownership.
Communicate the service state and review response evidence after the incident.
Put it to work
Route its alert, open an owned incident and follow the attached technical evidence.
Explore this workflowUse HTTP, certificate, domain or heartbeat monitoring and its configured response route.
Explore this workflowRead the response timeline and use reports to review the recorded handling of the case.
Explore this workflowYour first useful workflow
A configured route is useful when you have verified who it reaches and the evidence your team will use.
Choose a telemetry alert or external monitor for the condition you follow.
Read the guideA few useful answers
Creating and changing incidents, on-call schedules and escalation is included in Pro and Scale. Alerts to email, Slack, Telegram, PagerDuty and webhooks are on every plan.
HTTP endpoints, TLS certificate expiry, domain registration expiry and scheduled-job heartbeats share the monitoring and response workflow.
Yes. Your agent can read incident evidence and open or update an incident through MCP and the CLI. Changes preview first and apply only after you confirm.
Yes. HTTP endpoints, TLS certificates, domain expiry and scheduled-job heartbeats have external-monitoring workflows that connect to configured response routing.
Yes. An incident case can anchor an investigation of its lifecycle state, attached Issues or alerts, customer evidence and response timeline. Your agent reads it, and you open the case file to check.
Anectico / Private preview
Explore coordinated response and connected investigation with your agent in private preview.