A failing monitor or an alert opens an incident. Squasher adds the evidence and the likely cause, notifies your channel, and resolves it when the monitor recovers.
Free plan. No credit card required.
acmecheckout-apiIncidents
Search⌘ Kcheckout-api: error burst
SEV-2ResolvedTimeline
Created14:06
Monitor checkout errors failed: 41 error logs a minute.
Notification sent14:06
Posted to #incidents in Slack.
AI summary generated14:07
Squasher completed the automatic investigation.
Acknowledged14:09
Lina acknowledged the incident.
Resolved14:31
Monitor checkout errors recovered.
Example incident timeline
Every incident keeps its status, severity, timeline, and evidence in one place.
Failure and recovery thresholds open and resolve the incident without a person.
Datadog, Grafana, Prometheus Alertmanager, CloudWatch, PagerDuty, and generic webhooks.
Investigating, Identified, Monitoring, Resolved. SEV-1 to SEV-4, or rename them.
A summary, the likely root cause, next steps, and a suspect deploy from the hour before.
A private channel per incident, archived when it resolves and reopened with it.
Create a Linear issue from the incident for the work that remains.
Slack and Teams messages carry the impact, the likely cause, and the next step, not only a title.
#incidents
12SquasherAPP2:06 PM
checkout-api: error burst
Severity: SEV-2Status: Investigating
Started 4m after deploy of checkout-api@a41c
▸ Impact
Error logs on checkout-api went from 3 to 41 a minute. Checkouts return 500.
▸ Root cause
The errors began 4 minutes after checkout-api@a41c deployed. That release is the likely cause.
▸ Recommended action
Roll back a41c, or open the TypeError issue and run Create fix.
Monitor: checkout errors · Opened 2:06 PM
SquasherAPP2:31 PM
checkout-api: error burst
Severity: SEV-2Status: Resolved
Example alert.
Each change to the incident is an event: who did it, when, and what it said.
Example incidents and logs.
The incident workflow is live. Some tools in this space do more around it.
Checked against the product on 2026-10-20.
Add a monitor, add a destination, and let the next failure open the incident.
An HTTP check on a health URL is enough to start.
squasher monitors create-from-template --project "$SQUASHER_PROJECT_ID" http-health \ --inputs '{"url":"https://example.com/health"}'Connect Slack, or add Teams, Telegram, email, a webhook, or PagerDuty, on the default route.
Send Datadog, Grafana, or Alertmanager alerts in, so their incidents use the same routes.
Alert connectorsInstall Squasher for this project. If Squasher skills or MCP are not configured in this agent environment, run `bash <(curl -fsSL https://squasher.ai/install.sh) --agents -y`. Then read https://skills.squasher.ai/squasher-onboard/SKILL.md, map every runnable app/service/worker/frontend/agent in the repo, choose the matching Squasher SDK, log drain, OTLP, or Agent SDK path, initialize with SQUASHER_API_KEY and SQUASHER_PROJECT_ID from environment variables, send one real verification event, and report the files changed plus the verification step. Do not hardcode or reveal real API keys.
bash <(curl -fsSL https://squasher.ai/install.sh) --agents -yA failing monitor or a late heartbeat, an alert from Datadog, Grafana, Prometheus Alertmanager, AWS CloudWatch, PagerDuty, or a generic webhook, an anomaly finding, or a person in the dashboard. Repeat alerts for the same problem update one incident.
When a monitor opened it, yes. The monitor resolves the incident after the number of passing checks you set. You can also resolve, reopen, or change the status by hand.
It collects evidence, writes a summary, a likely root cause, and suggested next steps, and names a deploy that landed shortly before the incident. The incident assistant is on every plan.
No. After an incident is resolved, you can save a link to a post-incident review that you write elsewhere. The status page shows that link with the past incident.
Yes. A PagerDuty destination sends trigger, acknowledge, and resolve events with the incident ID as the deduplication key, so both tools stay in step.
No. Squasher plans have no seat fees. Incident management is on every plan.
Start free. Invite the whole team. AI triage is included on every plan.
For side projects, evals, and internal tools.
$0/ month
No card needed. No overage charges.
Start freeIncluded
For small production apps that want one tool, not five.
$29/ month
Flat price. No per-seat fees.
Start on ProEverything in Free, plus
For product teams replacing Sentry, replay, and status tooling.
$99/ month
Flat price. No per-seat fees.
Start on TeamEverything in Pro, plus
For high-volume teams with security, procurement, and support needs.
$299/ month
Flat price. No per-seat fees.
Start on ScaleEverything in Team, plus
Need more volume, a security review, or custom terms? Get in touch.
Add one monitor and one Slack channel, and see the evidence arrive with the alert.
Free plan. No credit card required.
