Skip to content

new relic custom agent incident response#1560

Merged
aaronpowell merged 3 commits intogithub:stagedfrom
newrelic-partners:staged
Apr 30, 2026
Merged

new relic custom agent incident response#1560
aaronpowell merged 3 commits intogithub:stagedfrom
newrelic-partners:staged

Conversation

@jcountsNR
Copy link
Copy Markdown
Contributor

@jcountsNR jcountsNR commented Apr 29, 2026

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the staged branch 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

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

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.

Copilot AI review requested due to automatic review settings April 29, 2026 17:16
@jcountsNR jcountsNR requested a review from aaronpowell as a code owner April 29, 2026 17:16
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 29, 2026

🔍 Skill Validator Results

⛔ Findings need attention

Scope Checked
Skills 1
Agents 1
Total 2
Severity Count
--- ---:
❌ Errors 2
⚠️ Warnings 0
ℹ️ Advisories 0

Summary

Level Finding
[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.
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}

</details>
> **Note:** The validator returned a non-zero exit code. Please review the findings above before merge.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 thread docs/README.agents.md Outdated
Comment thread agents/new-relic-incident-response.agent.md
Comment thread agents/new-relic-incident-response.agent.md
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
jcountsNR and others added 2 commits April 29, 2026 13:02
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@aaronpowell
Copy link
Copy Markdown
Contributor

Sorry about the pain with the other PR @jcountsNR - but this is all good and merged.

@aaronpowell aaronpowell merged commit a2b0924 into github:staged Apr 30, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants