Incident response
Vendor-neutral coverage of incident response.
Articles
9 articlesBuilding your own AI SRE moves the toil; it does not remove it
Chronosphere leaders argued in The New Stack that engineering teams should build their own AI SRE to map systems, investigate incidents and support reliable delivery at scale. The operational read is narrower: an in-house AI SRE is a second production system with its own on-call, its own change-management story and its own place in the audit trail.
Aug 2, 2026 · Maya OkonkwoIncident responseAWS teaches its DevOps Agent to open the pull request too
An AWS DevOps Blog walk-through chains the AWS DevOps Agent with the Kiro CLI so incident findings become a pull request instead of a Slack thread. The pipeline still gates on human approval, but who wrote the diff has changed, and so has what your review is actually catching.
Jul 15, 2026 · Tomás VegaIncident responseSurvey: 93% of large North-American IT shops have hit an AI-coding incident
A poll of 406 IT decision makers at North American organizations with more than 250 employees finds nearly all of them have logged at least one infrastructure incident attributable to AI coding tools, a number CI/CD owners can quote when arguing for tighter merge gates on agent-generated changes.
Jun 29, 2026 · Maya OkonkwoIncident responseHCP Vault Dedicated opens cluster DR drills, by support ticket only
HashiCorp put cluster disaster recovery for HCP Vault Dedicated into public preview, giving teams a way to simulate cluster-level failures and prove their failover path. The drill is gated through HashiCorp support, not the customer's own runbook.
Jun 28, 2026 · Maya OkonkwoIncident responseGitHub ships a one-click self-revoke for users whose credentials just leaked
An individual GitHub Enterprise member can now wipe every credential they own, personal access tokens, SSH keys, OAuth tokens and SSO authorizations, in a single action from the Settings page. Containment used to be a scavenger hunt across four menus.
Jun 25, 2026 · Tomás VegaIncident responseAWS wires its DevOps Agent into PagerDuty incidents
AWS has paired its DevOps Agent with PagerDuty so that the moment an incident is created, the agent runs a root-cause investigation across AWS telemetry, deployment history and a short list of third-party observability tools, posting its findings back onto the incident record.
Jun 21, 2026 · Maya OkonkwoIncident responseAWS DevOps Agent reaches GA with the Datadog MCP Server in tow
AWS has moved its DevOps Agent from preview to general availability, shipping it alongside the Datadog MCP Server so the agent can correlate monitoring signals with AWS-deployed infrastructure during an incident. The badge change is the smaller story; the bigger one is what SRE teams now have to write down before the agent touches production.
Jun 20, 2026 · Maya OkonkwoIncident responseAWS teaches its DevOps Agent to flip feature flags during incidents
The AWS DevOps Blog details an integration where the AWS DevOps Agent's MCP server talks to LaunchDarkly so an agent can identify and toggle the flags relevant to a live outage instead of paging three teams to do it by hand. The integration removes a real coordination step, and forces every shop to write down which actions an agent is allowed to take unattended.
Jun 20, 2026 · Tomás VegaIncident responseAWS pushes its DevOps Agent's diagnostic reach down to the EKS node via a custom MCP server
AWS has published a pattern for extending its autonomous DevOps Agent into EKS node OS and runtime data through a custom Model Context Protocol server, addressing incidents that live outside the agent's native cluster-control-plane visibility. The post is explicit that the implementation is a proof of concept, not a production replacement for monitoring or log shipping.
Jun 17, 2026 · Maya Okonkwo