moneat.io

Turn one alert into coordinated action.

Page the right person, open the right channel, and keep your team and customers informed from first alert to resolution.

Start freeSee how it runs

Start free · On-Call available on eligible plans

moneat.io/on-call/alerts/alr_7f21c4
Alerts / alr_7f21c4
PRMHJO+3
Update status
P1
Triggered
api-checkout
prod / eu-west-1
Checkout latency above SLO — p95 4.2s against a 900ms objective
Opened 14:02:1100:04:18Route prod-criticalEscalation L1Lead —
Timeline
Responders0
PRPriya Raman—
MHMarcus Hale—
JOJonas Ohlinobserver
Linked signals
Trace
POST /checkout4.2s
Logs
pool timeout1.4k
Deploy
api-checkout 2f91c13:58
Follow-ups
Raise pool ceiling on api-checkout
Add SLO burn alert at 2× rate
Slack
# inc-4026
Message #inc-402
Alert route
prod-criticalrevision 4 · 11 sources
Match
service = api-checkout
env = prod
severity >= sev2
Grouping
0alerts on one key
checkout.latency.p95 · window 60s
Escalation
L1Priya Raman
waiting
L2Payments rota
—
L3Marcus Hale
—
auto-resolve on recoveryidle
 
 
 
Moneatnow
P1 · api-checkout
Checkout latency above SLO. You are on call. Acknowledge within 4:00.
BackAlert
P1Triggered
Checkout latency above SLO
p95 is 4.2s against a 900ms objective on api-checkout, prod / eu-west-1.
Open for
52s
Escalates in
3:08
Details
SourceSLO burn
Triggered14:02:12
Escalation policyprod-critical
Acknowledge
Resolve
Alerts2IncidentsOn-callSettings
Drag any window · scroll to open the room

Everything you need to investigate an incident.

Explore errors, logs, traces, profiles and session replays in one place.

  1. Grouped, deduplicated, and tied to the release that introduced them.

    Open error tracking

  2. Structured, searchable and live. Tail a service without leaving the incident.

    Open logs

  3. Every span of the slow request, with the one that waited drawn in red.

    Open traces

  4. Your metrics, your queries and your own databases, on one board.

    Open dashboards

  5. Rotations, overrides and the gap at 03:00, found before it pages.

    Open on-call

  6. What the user saw, synced to the error they hit.

    Open session replay

  7. The hottest paths in production as a flamegraph, per release.

    Open profiling

  8. Roll out by percentage, target by attribute, and kill it in one click.

    Open feature flags

  9. Every check with its result and response time, over the window you pick.

    Open uptime

  10. Tell customers from inside the incident, on your own domain.

    Open status pages

  11. Every host and container, ranked by what is running hot.

    Open infrastructure

Coordinate your response in Slack.

Bring responders into one channel, assign roles, and post updates to the incident and the status page from the same command.

Slack
Search Acme
# inc-417-search-5xx3
Today
Moneat opened this channel for INC-417 · 9:41 AM
MoneatApp9:41 AM
SEV-2
INC-417 · Search 5xx after v2.41.0
Lead: Priya Raman
Communications: Marcus Hale
Status page: status.acme.io · Resolved
Responders: 3
Take a rolePost updateOpen timeline
Marcus Hale and Ana Sousa joined · 9:42 AM
MoneatApp9:42 AM
Change
search-api v2.41.0 rolled out to prod-eu at 9:36 AM
Deployed by Ana Sousa. 5xx rate went from 0.2% to 4.1% within two minutes of the rollout, on 12 of 12 pods.
matched from deploy markers · search-api · prod-eu
Open deployCompare traces
AS
Ana Sousa9:43 AM
that's mine, the ranking cache change. rolling back now
🙏 1
MH
Marcus Hale9:44 AM
/moneat update rollback of v2.41.0 in progress, search degraded in eu-west
MoneatApp9:44 AM
Update posted to #inc-417-search-5xx and to status.acme.io as Identified. Marcus Hale has communications from here.
MoneatApp9:49 AM
Recovered
search-api v2.40.3 healthy on 12 of 12 pods
5xx rate at 0.1% for five minutes. Alert group ag_9c1e42 has cleared.
Mark monitoringResolve incident
PR
Priya Raman9:53 AM
/moneat resolve
MoneatApp9:53 AM
Resolved
INC-417 · 14 minutes, 3 responders
Status page: status.acme.io · Resolved
Postmortem: Drafted from 11 timeline entries
Follow-ups: 1 captured, needs an owner
Open postmortemAssign follow-up
✅ 3
Message #inc-417-search-5xx
Aa

Closing it hands the whole timeline to the postmortem.

Do it all,
right from the terminal

Connect your favourite AI agent. It reads the issue, pulls the trace and posts the update, without leaving the window you write the fix in.

Learn more
claude — ~/acme/checkout-api
Claude Code v2.1.4
Welcome back!Opus 5 · Max~/acme/checkout-api
MCP serversmoneat · connected · 160+ toolsread issues, traces, logs, hostswrite incidents, status pages
>checkout is timing out — what changed?
moneat -list_issues(service: 'checkout-api', status: 'unresolved')
4 issues · TimeoutError up 38× in the last hour
moneat -get_issue(id: 'CHECKOUT-4182')
pool exhausted · 1 284 events · first seen 13:58
moneat -get_trace(trace_id: 'a41f…9c2')
2.41s end to end · 1.9s waiting on a connection
moneat -list_releases(service: 'checkout-api', limit: 3)
2f91c · 13:58 · “raise checkout concurrency”

The 13:58 release took worker concurrency to 64 against a pool of 20. Everything past the twentieth request waits for a connection, which is the 1.9s. Cap concurrency or raise the pool.

>ack the page and tell the status page
moneat -list_on_call_alerts(service: 'checkout-api')
1 open · L1 paged 14:02 · unacknowledged
moneat -post_incident_update(incident: 'INC-402', body: 'Pool exhaustion from 2f91c…')write
posted to the timeline and #inc-402
moneat -update_status_page_incident(page: 'status.acme.io', status: 'identified')write
published · 412 subscribers notified

Acknowledged, and INC-402 now carries the trace, the release and the pool numbers. The status page says identified.

>
? for shortcutsmoneat mcp · 160+ tools

Make the next incident less of a scramble.

Get alerts to the right person and give your team one place to manage the response. On-Call is available on eligible plans.

Start freeRead the docs