new relic custom agent incident response#1560
Merged
aaronpowell merged 3 commits intogithub:stagedfrom Apr 30, 2026
Merged
Conversation
Contributor
🔍 Skill Validator Results⛔ Findings need attention
Summary
Full validator output```text Found 1 agent(s) ❌ [agent:New Relic Incident Response Agent] Agent name 'New Relic Incident Response Agent' does not match filename 'new-relic-incident-response.agent.md' (expected 'New Relic Incident Response Agent.agent.md'). ❌ [agent:New Relic Incident Response Agent] Agent name 'New Relic Incident Response Agent' contains invalid characters — must be lowercase alphanumeric and hyphens only. Validated 1 agent(s){Ansi.Red}Agent spec conformance failures — fix the errors above.{Ansi.Reset} |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new custom agent intended to guide incident response workflows using New Relic observability data, and registers it in the agents documentation list.
Changes:
- Added a new “New Relic Incident Response Agent” definition under
agents/. - Added the agent entry (with install links) to
docs/README.agents.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/README.agents.md | Adds a new row linking to the New Relic incident response agent. |
| agents/new-relic-indident-response.agent.md | New agent prompt content for New Relic-driven incident triage and debugging. |
Comment on lines
+26
to
+36
| 1. **Understand the Alert** | ||
| - Use the New Relic MCP server to retrieve details about the active alert(s) | ||
| - Identify which entity is affected (APM application, host, service, etc.) | ||
| - Determine the alert condition that triggered (error rate, response time, throughput, etc.) | ||
| - Assess severity, duration, and whether the alert is still firing | ||
| - Check for correlated alerts across related entities | ||
|
|
||
| 2. **Establish Timeline** | ||
| - Query when the issue started (alert violation begin time) | ||
| - Use the New Relic MCP server to retrieve recent change tracking events (deployments) for the affected entity | ||
| - Identify if there were deployments, configuration changes, or infrastructure changes around the incident start time |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
aaronpowell
approved these changes
Apr 30, 2026
Contributor
|
Sorry about the pain with the other PR @jcountsNR - but this is all good and merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.stagedbranch for this pull request.Description
Following up from #1483 and closing that PR because it was having issues from merging from main branch. This is a new GH custom agent for New Relic.
Type of Contribution
Additional Notes
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.