Incident Response
Run incidents without leaving Google Chat.
All the context, all the automation, all your tools, all in one platform that helps you resolve issues faster and with less effort.
incident-20250915-customer-cannot-checkout
Rootly App 1:30 PM
Elevated 5xx errors on checkout SEV1
Sharp drop in successful transactions, likely caused by recent changes in the payment authorization flow. Eng team investigating.
View in RootlyOpen Incident Space
Allen Ruiz 1:31 PM
@Rootly show me your root cause analysis
Rootly App 1:31 PM
Investigating…Root cause analysis
Deploy v2.41.0 of payments-service at 14:30 UTC introduced a connection leak on the payments Postgres primary, exhausting the pool. Error rate rose from 0.2% to 18% within two minutes.
High confidenceSuggested fix: roll back to v2.40.3
Fix issues faster, consistently—with fewer people and less effort.
Incident management with built-in AI to automate your workflows for faster resolutions—directly in Google Chat.
Google Chat-native →All the context, all your tools, all the collaboration—where you’re already working.
Natively AI →Real-time scribe, summaries, and proactive suggestions—all built in. Just chat with the Rootly agent.
Workflows →Automate incident workflows in seconds—best practice templates or tailored to your needs.
Communications →Instantly update the right people, across every channel, from a single place.
Elevated 5xx errors on checkout API after payments-service…
Started
- Severity
- SEV 1
- Started at
- July 10, 2026 09:37
- Type
- Customer Facing
Summary
Starting around 14:32 UTC, the checkout API began returning 5xx errors at roughly 18% of requests, up from a baseline near 0.2%. The spike lines up with the 14:30 rollout of payments-service v2.41.0.
See in Rootly
3 replies · 10 min
Adam Frank added a new event to the timeline: Jira Issue has been created
View in Rootly
Rootly added a new event to the timeline: Google Meeting has been created
Google MeetA call has been created for this incident.
Join Call
incident-20250915-customer-cannot-checkout
Tyler Moss 1:56 PM
@Rootly I joined late. What's going on?
Rootly App 1:56 PM
Here's what you missed
- Customers have been unable to complete purchases due to checkout failures.
- The cause is intermittent timeouts with our payment provider's API, starting about 45 minutes before detection.
- Alex is rolling back, and Florence just updated the status page.
Join meeting
Recording in progress
- When
Incidentis Active - When
Typeis Security - When
Severityis SEV0 - When
Serviceis Updated - When
Followupis Created
Create Retro in Confluence
Send a Google Chat message
Create a Linear issue
Pull Datadog metrics
Fetch GitHub commits
Email (Desktop)Email (Mobile)SMS
Google Chat
Some customers are unable to check out. We've identified the issue and are working on a fix. Next update in 30 min.
Sent to 2 audiences
From alert to organized response, in one space.
The moment an incident starts, Rootly spins up a dedicated Google Chat space, invites responders, and posts a live incident overview card—severity, status, roles, and next steps in one place. No hunting for the right thread. No blank space.
Elevated 5xx errors on checkout API after payments-service…
Started
- Severity
- SEV 1
- Started at
- July 10, 2026 09:37
- Type
- Customer Facing
Summary
Starting around 14:32 UTC, the checkout API began returning 5xx errors at roughly 18% of requests, up from a baseline near 0.2%. The spike lines up with the 14:30 rollout of payments-service v2.41.0.
See in Rootly
3 replies · 10 min
Adam Frank added a new event to the timeline: Jira Issue has been created
View in Rootly
Rootly added a new event to the timeline: Google Meeting has been created
Google MeetA call has been created for this incident.
Join Call
Announcements and updates, automated.
Rootly posts to a shared announcement space so leadership and stakeholders stay current without joining the response. Status changes flow out automatically—the people fixing the problem stay focused on fixing it.
Email (Desktop)Email (Mobile)SMS
Google Chat
Some customers are unable to check out. We've identified the issue and are working on a fix. Next update in 30 min.
Sent to 2 audiences
AI directly in the space to help you with almost anything.
@Rootly in Google Chat and the agent will answer your questions in plain language and takes actions on your behalf, as your user, within your permissions: page someone, change severity or status, manage action items, draft comms, get caught up, generate a full analysis to improve, and so much more.
Thread
JJ Tang 11:29 AM
@Rootly what action items did I forget to document? Assign them to Jamie Baker.
Rootly App 11:29 AM
The undocumented action items from this thread are captured and assigned to Jamie Baker.
High priority
- 1Page Data Platform on-call for DLQ replayJamie B.
- 2Confirm 11 missing fields in v5 mappingJamie B.
- 3Re-update status page, which still shows resolvedJamie B.
- 4Notify affected merchantsJamie B.
Medium priority
- 5Add an Elasticsearch field count alertJamie B.
A retrospective process that runs itself.
AI retros with customizable blocks that capture every action, then draft the summary, impact, root cause, and more. All editable, with tasks tracked to done.
API Latency Degradation (INC-2034)
Summary
Between 14:03 and 15:45 UTC on July 9, the public API experienced elevated latency and intermittent 5xx errors across all regions. A runaway Redis connection pool exhausted backend thread workers, leading to cascading timeouts in downstream services.
Root cause
A deployment on July 8 introduced a usage-metrics feature that stored high-frequency user events in Redis.
Your best incident response, made repeatable.
One intuitive and powerful platform, from the first alert to the final action item.
9:41
Rootly · now
High: Redis Engine CPU High
production-redis-002 · You're on call for Messaging
Slide to ack‹ #jetdhv · Leader · High
Redis | Engine CPU High production-redis-002 [PRODUCTION]
DetailsTimelineGroupPayload
Summary Generated 10:22 AM
Redis CPU on production-redis-002 spiked to 96% after a message queue storm from one customer's rescheduled jobs. Messaging updates are delayed for several customers, and CPU is falling as mitigations land.
Source link
See in Datadog ↗
On-call, built in
Modern on-call that pages the right person, the first time.
Causes6 entities
Services3 entities
Teams4 entities
Catalog context
A service catalog that makes every incident smarter.
Rootly App
What I've found so far
Likely root cause
A transient spike in message production is the primary trigger, at 23:09 UTC within the alert's 5-minute window.
AI root cause analysis
AI that surfaces probable root cause and suggests fixes for you.
Status
All systems operational
ChatOperational
Status pages
Beautiful, automated status pages that keep your customers informed.
#inc-260402Technical response
inc-260402Business responsePrivate incidents
Sensitive incidents are always scoped to the people who should see them, and no one else.
>_ MCP
Claude CodeCursorWindsurf
API, MCP, and Terraform
Manage incident response as code, the way your team ships everything else.
Hundreds of integrations ready to go.
Connect all your existing alerting sources—and extend further with our Terraform provider, API, or MCP server.
Explore all integrations

You and your teams deserve modern incident management.
Frequently asked questions
Everything you need to know about Incident Response with Google Chat.
What is Rootly Incident Response?
Rootly enables engineering teams run the entire incident inside Slack, Microsoft Teams, and Google Chat — declaring, assigning roles, coordinating the fix, updating stakeholders, capturing the timeline, and more. Because it's part of one platform, each incident inherits context from on-call, the service catalog, and past incidents, so response starts a step ahead.
Does Rootly work in Slack, Microsoft Teams, and Google Chat?
Yes. The full incident lifecycle runs natively in Google Chat, Slack, and Microsoft Teams—declaration, coordination, comms, AI assistance, and retrospectives—without switching to a separate interface.
What does Rootly's Google Chat integration do?
When an incident starts, Rootly creates a dedicated Google Chat space, invites responders, and posts real-time incident overview cards. Teams can run the incident with slash commands and emoji shortcuts, post automated updates to announcement spaces, and connect on-call alerting — the full incident workflow, inside Google Chat.
How does the integration connect to Google Workspace?
The recommended production setup uses a service account with domain-wide delegation, configured by a Workspace admin — this enables rich incident cards, slash command dialogs, and emoji reactions. A simpler OAuth option is available for quick evaluation.
Can we use Google Chat alongside Slack or Microsoft Teams?
Yes. Rootly supports multiple chat integrations simultaneously, with workflows that route incidents to specific platforms based on conditions — useful for mixed workspaces, migrations, or acquisitions.
What permissions does Rootly need?
The service account requires six Google Chat scopes for creating spaces, managing members, and sending messages. The full scope list is in the installation guide, and setup is controlled by your Workspace admin.
Does the rest of Rootly work with Google Chat incidents?
Yes. Incidents in Google Chat are full Rootly incidents — connected to on-call schedules, catalog context, workflows, status pages, and retrospectives like any other.








