AI incident summaries
Plain-English summaries of every incident — what happened, what changed, and the likely cause — generated the moment an alert fires.
Quick answer#
Every incident gets a 2–3 sentence AI summary pinned to the top: what triggered, which check, which region, and the closest recent change (deploy, DNS, cert).
What the summary includes#
Where to find it in Lemwatch#
Incident detail → Summary. Also posted to Slack / email alerts when integration is on.
How to trust it#
FAQ#
Which model powers it?#
Lemwatch AI Gateway — model choice is abstracted; upgrades happen server-side.
Does it count against my AI quota?#
Yes — see AI usage and quotas.
Related#
Related Articles
AI root-cause analysis
For every incident Lemwatch correlates recent deploys, DNS diffs, cert changes, and upstream provider status pages to pinpoint the likely cause.
What is Autopilot in Lemwatch?
Autopilot watches your sites, triages incidents, and executes safe remediations — from acking flappy alerts to re-running suspected false positives.
Alert confirmation gates
Lemwatch confirms a failure from multiple regions before alerting, so single-region blips stay quiet.
Incident Management Workflow
Acknowledge, investigate, and resolve incidents with your team.