---
title: "eve Incident Response Agent"
description: "Investigate incidents in Slack with an eve agent that tests hypotheses against Datadog, GitHub, and Vercel data and cites sources."
url: "https://vercel.com/templates/eve/eve-incident-response-agent"
links:
  repository: "https://github.com/vercel-labs/eve-sre-agent-template"
  demo: "https://vercel.com/kb/guide/eve-incident-sre-agent"
  deploy: "https://vercel.com/new/clone?demo-title=eve+Incident+Response+Agent&demo-description=Investigate+incidents+in+Slack+with+an+eve+agent+that+tests+hypotheses+against+Datadog%2C+GitHub%2C+and+Vercel+data+and+cites+sources.&demo-url=https%3A%2F%2Fvercel.com%2Fkb%2Fguide%2Feve-incident-sre-agent&project-name=sre&repository-name=sre&repository-url=https%3A%2F%2Fgithub.com%2Fvercel-labs%2Feve-sre-agent-template%2Ftree%2Fmain&from=templates&products=%5B%7B%22type%22%3A%22blob%22%2C%22access%22%3A%22private%22%7D%5D&connect=%5B%7B%22type%22%3A%22slack%22%2C%22env%22%3A%22SLACK_CONNECTOR%22%2C%22triggers%22%3Atrue%2C%22triggerPath%22%3A%22%2Feve%2Fv1%2Fslack%22%7D%2C%7B%22type%22%3A%22github%22%2C%22env%22%3A%22GITHUB_CONNECTOR%22%7D%2C%7B%22type%22%3A%22datadog%22%2C%22env%22%3A%22DATADOG_CONNECTOR%22%7D%2C%7B%22type%22%3A%22vercel%22%2C%22env%22%3A%22SRE_VERCEL_CONNECTOR%22%7D%5D&demo-image=%2F%2Fimages.ctfassets.net%2Fe5382hct74si%2F2palFAjg8CYiPZQAHmfto8%2Faabcf81e4fb2b464fbfb59ad5737d582%2Feve-incident-response-3x.png"
---

# eve Incident Response Agent

Investigate incidents in Slack with an eve agent that tests hypotheses against Datadog, GitHub, and Vercel data and cites sources.

# eve Incident Response Agent

[eve Incident Response Agent](https://github.com/vercel-labs/eve-sre-agent-template), named sre, is a Slack AI agent for investigating production alerts and incidents. It checks possible causes against Datadog, GitHub, Vercel, and other connected operational sources, then reports findings with source links. The default investigation workflow is read-only, leaving responders to decide what action to take.

## What can you build with this template?

Give your team an investigator they can call from an incident conversation or connect to an alert source. Investigations can start through:

- A Slack mention or direct message to the agent.
- A new top-level message in a watched Slack channel.
- An authenticated `POST /v1/investigate` request from an external system.

The agent tests hypotheses against live signals and records findings that affect the investigation. Each turn has its own evidence set, with duplicate finding-and-URL pairs recorded once. Slack replies put the conclusion first and include evidence so responders can inspect the source.

You can build AI agents for your team's operational workflows by changing the investigation instructions and skills or adding connections to other systems. Saved runbooks let recurring alerts use procedures created through Slack.

## Why use this template?

Teams evaluating artificial intelligence agents for on-call work can inspect the sources behind sre's conclusions and adapt its investigation procedures to their services. The template connects incoming alerts to an investigation and a Slack response, giving responders an explanation they can check against their monitoring and deployment data.

The best AI agent for an incident workflow must be able to access the evidence that workflow requires. Check the credential model before enabling unattended investigations: automated runs use service-authenticated tools and supplied metadata, while a Slack user's Vercel connection requires that user's authorization.

## Why use eve on Vercel?

The [eve AI agent framework](https://vercel.com/docs/frameworks/agents/eve) provides the agent's instructions, tools, and channels. Vercel Connect supplies the integrations used to gather operational data, so you can extend the investigation without replacing its Slack entry point or reporting workflow.

Private Vercel Blob stores channel-watch configuration and saved custom runbooks. These are optional features; Blob is not required for every investigation. Global runbooks apply across sessions, while personal runbooks belong to the requesting Slack user.

## What should you know before deploying?

The deploy flow provisions Slack, GitHub, Datadog, and Vercel MCP connectors plus private Blob storage. Use read-only GitHub and Datadog permissions. Invite the bot to the target Slack channel and confirm that a mention receives a reply before enabling automation. The [setup guide](https://github.com/vercel-labs/eve-sre-agent-template/blob/main/docs/setup-for-agents.md) covers CLI configuration and connector credentials.

For webhooks, configure `WEBHOOK_SECRET` and send it in the `x-sre-webhook-secret` header or as an `Authorization: Bearer` token. The [automation guide](https://github.com/vercel-labs/eve-sre-agent-template/blob/main/docs/automate-investigations.md) documents request fields and delivery checks. An accepted request schedules the investigation; confirm its Slack thread separately.

Automated webhook and channel-watch runs have no requesting user's OAuth identity. They cannot use the user-authorized Vercel connection, even when that connector exists on the project. Choose service-authenticated sources for the investigations you want to start unattended.

## Frequently asked questions

### How do I start an investigation in Slack?

Mention sre or send it a direct message. You can also configure a watched channel so new top-level messages can trigger investigations, or send an authenticated request to the investigation webhook. The bot must belong to the Slack channel receiving the investigation.

### Can I check the evidence behind an incident finding?

Yes. sre attaches source links to recorded findings and includes that evidence in its Slack result. Evidence belongs to the current investigation turn, so a later turn starts its own set instead of inheriting the previous turn's recorded findings.

### Does sre remediate production issues automatically?

No, the default workflow is a read-only investigation that reports its conclusions. Configure read-only permissions for GitHub and Datadog as part of setup. The investigation instructions and the permissions you grant connectors are separate controls.

### Can an automated investigation use my Vercel authorization?

No. Webhook and channel-watch investigations run with service identities and cannot borrow a Slack user's OAuth connection. They use the supplied incident context and available service-authenticated tools; Vercel's user-authorized tools require an investigation associated with an authorized Slack user.

### How do saved runbooks affect later investigations?

Ask sre in Slack to create a runbook for a recurring issue. Global runbooks apply to all sessions, and a user's personal runbook takes precedence over a global one with the same name. A newly saved runbook loads on a later matching request, not during its creation request, and saving or loading it requires private Vercel Blob storage.

## Related resources

- [Set up and extend an incident investigation agent](https://vercel.com/kb/guide/eve-incident-sre-agent)
- [Incident agent source and local development instructions](https://github.com/vercel-labs/eve-sre-agent-template)

## Related Templates

### [eve Contentful Agent](https://vercel.com/templates/eve/eve-contentful-agent)

Manage Contentful from Slack with eve. Query synced content, edit drafts, upload assets, and review publication requests.

### [eve Marketing Team](https://vercel.com/templates/eve/eve-marketing-team)

Coordinate a marketing lead and five specialist agents in Slack, with Notion drafts, Typefully posts, and Resend email campaigns.

### [eve Software Factory](https://vercel.com/templates/eve/eve-software-factory)

Turn GitHub and Linear issues into reviewed draft pull requests with specialist eve agents and human approval before shipping.

---

## Additional documentation

The [Vercel Knowledge Base](https://vercel.com/kb) contains guides and answers to common questions about Vercel, including deployment, framework configuration, domains, caching, and troubleshooting.
