AWS 
Azure 
Datadog 
Grafana Four dimensions that matter in production
Cleric 
PagerDuty SRE Agent Any production signal: alerts, Jira tickets, customer escalations, Slack threads, metric anomalies, or scheduled proactive scans.
Incidents routed through PagerDuty's event pipeline.
Cross-stack: cloud, code, deploys, observability tools, and team context.
Connected observability tools, knowledge bases, incident history, and runbooks. Strong within the PagerDuty incident boundary.
Can reason about novel problems without existing runbooks. Escalates when it isn't sure.
Learn moreRuns approved automations that match known problem patterns. Humans decide for anything outside pre-approved workflows.
Verifies whether the diagnosis was correct and the fix resolved the root cause.
Learn moreConfirms that services were restored after running an automation.
Cleric Any production signal: alerts, Jira tickets, customer escalations, Slack threads, metric anomalies, or scheduled proactive scans.
PagerDuty SRE Agent Incidents routed through PagerDuty's event pipeline.
Cleric Cross-stack: cloud, code, deploys, observability tools, and team context.
PagerDuty SRE Agent Connected observability tools, knowledge bases, incident history, and runbooks. Strong within the PagerDuty incident boundary.
Cleric Can reason about novel problems without existing runbooks. Escalates when it isn't sure.
Learn more PagerDuty SRE Agent Runs approved automations that match known problem patterns. Humans decide for anything outside pre-approved workflows.
PagerDuty SRE Agent Confirms that services were restored after running an automation.
PagerDuty SRE Agent is an agent. Cleric is an autonomous learning system.
Cleric PagerDuty SRE Agent Learns service topology, past issues and your engineering conventions.
Recognizes a meaningful production issue.
Correlates evidence to explain what happened.
Takes action or routes to the right human.
Checks whether the fix actually worked.
Improves future work from resolved outcomes.
Learns service topology, past issues and your engineering conventions.
Cleric PagerDuty SRE Agent Recognizes a meaningful production issue.
Cleric PagerDuty SRE Agent Correlates evidence to explain what happened.
Cleric PagerDuty SRE Agent Takes action or routes to the right human.
Cleric PagerDuty SRE Agent Checks whether the fix actually worked.
Cleric PagerDuty SRE Agent Improves future work from resolved outcomes.
Cleric PagerDuty SRE Agent When to choose PagerDuty
PagerDuty owns incident coordination: on-call schedules, escalation policies, stakeholder notifications, status pages, post-incident reviews, and multi-team communication. If your problem is getting the right people on the call and keeping stakeholders updated, choose PagerDuty.
Bottom line
PagerDuty's SRE Agent responds to incidents, runs approved automations, and confirms restoration. Cleric investigates any production signal, handles novel problems, and verifies whether the diagnosis was correct.
See how Cleric investigates your production issues
Setup takes minutes. Read-only by default. See how Cleric investigates production issues across your full stack.
Information about PagerDuty SRE Agent is based on publicly available data as of May 2026 and may not reflect the most current features or pricing. All third-party trademarks referenced on this page are the property of their respective owners. Cleric is not affiliated with, endorsed by, or sponsored by PagerDuty.