Cleric Named a Gartner® Cool Vendor in AI for SRE and Observability.

Find out more
Start free trial
Start free trial

Prevent incidents

Agents that check every production change, then fix regressions before customers notice.

Start free trial Book a demo
New issue
Issues Changes Chats Knowledge Automation Performance

Admin

Docs System Health Integrations Settings Log out
Changes CHG-48

Tighten timeout handling

Resolved

#1849 @maya v2.14.0 Deployed Sep 15 at 09:41 # eng-checkout checkout-api

Summary

Strict timeouts for checkout's downstream calls

Expectations

Checkout calls use the new timeout Verified

Checkout p95 latency stays at baseline Anomaly found

p95 latency 182 ms → 511 ms

200 ms 400 ms PR #1849
09:2009:3009:4009:5010:0010:1010:2010:30

The fix

Resolved

PR #1893: Revert CHECKOUT_V2_STRICT_TIMEOUT

  1. 10:22 Cleric opened the fix PR
  2. 10:31 Approved by Maya
  3. 10:52 Deployed and verified, p95 back to 180 ms
Thread #eng-checkout

Cleric APP 9:50 AM

⚠️ Anomaly found: p95 up after PR #1849

1 reply

Cleric APP 10:52 AM

✅ Resolved: the regression I flagged has been fixed.

  • Intent: strict timeouts, verified
  • Regression: p95 +329 ms, now fixed, back to 180 ms
Open in Cleric

5 min

Time to Root Cause

92%

Actionable Findings

200,000+

Production-Grade Investigations

After the merge

Ship. Move on

Once you ship, Cleric checks your release and lets you know how it went. It fixes regressions and stays on call for you.

The team loves Cleric. The biggest challenge isn’t finding ways to use it, it’s deciding where to use it next. It consistently helps us uncover issues faster and shorten the path from problem to solution.
Priya Sawant
Priya Sawant Senior Vice President of Engineering
Cleric consistently delivers precise, accurate results. It’s clear the product was built by platform engineers who have lived the realities of operating production systems.
Amina Odžak
Amina Odžak Head of Product Quality & Security
No one’s going to the Cloudflare dashboard anymore. No one’s going to the Datadog dashboard anymore, even though they’re set up. The go-to is Cleric.
Affaf Ahtisham
Affaf Ahtisham Head of Engineering
I see Cleric functioning as an SRE companion for our Software Engineers. If one team has already solved an alert, we can apply that knowledge elsewhere.
Read case study
Maxime Fouilleul
Maxime Fouilleul Head of Infrastructure & Operations
Cleric in action

Stay ahead of failures

Cleric checks your releases, handles your alerts, and gets fixes ready for you to review.

Ship without the worry

Focus on what you’re building next while Cleric checks your changes in production and catches regressions, even days later.

Change Verification · PR #1902 Release verified

cart-apiBatch price lookups

What Cleric is checking

Read from the PR when it merged.

Cart load p95 No increase Price mismatches Stays at zero DB connections Within pool limit

Checks over 14 days

Day 14 of 14
  1. Day 1 Deployed · first check passed
  2. Day 3 Weekday peak traffic · passed
  3. Day 7 Full sales cycle · passed
  4. Day 14 Window closed · no deviation
Cleric sent you the all-clear

Give the pager to Cleric

Cleric handles your alerts and closes false positives, so you only get paged when you’re needed, with the findings ready.

Works inside your

&
On-call · last 24 hours Live

47 alerts reached Cleric

41 Closed as false positive
5 Investigated and fixed by Cleric
1 Escalated to an engineer
INV-1247payment-api 02:31

The one that reached you · p99 latency regression

Why you Rollback needs a schema decision Cause Retry storm, PR #470 Evidence 7 signals attached
Open investigation
Engineers woken for noise: None

Solve complex production issues

Cleric brings you the cause, the evidence, and a fix PR to review, then checks that the issue is resolved after the fix deploys.

PR #1893checkout-api Ready for review

RevertCHECKOUT_V2_STRICT_TIMEOUT

config/checkout.yaml 1 file changed
-strict_timeout: true +strict_timeout: false

Why this fixes it

p95 latency rose 4 min after deploy Isolated to checkout-api Same revert fixed INV-1182

Every line links to the production data behind it.

Waiting on you Request changes Approve
Under the hood

Simple on the surface. Serious underneath

Cleric draws on your stack and past investigations to find the cause, then checks that your fixes work in production.

Knows your stack

Cleric maps services, dependencies, and ownership to trace regressions across systems.

Knows your stack

Verifies its work

Cleric checks each deployed fix against the live environment to confirm that the issue is resolved.

Verifies its work

Compounds over time

Cleric learns from each fix and carries that context into future investigations.

Compounds over time
Peek under the hood
Security-first

Paranoid by design

Read-only by default. Every action logged, every investigation auditable. SOC 2 Type II compliant, with regular manual penetration testing. Your data encrypted everywhere and never used for training.

Learn more in our Trust Center
Security overview
Integrations

Built to plug right into your stack

Connect your whole stack in an afternoon. Read access by default, write access when you’re ready.

See if Cleric is a fit for your stack

Catch failures before your customers do

Put Cleric to work on your production changes.

Start free trial Book a demo