Skip to main content
subagent CX Codex official · GitHub

New Relic APM Agent — GitHub Copilot subagent

GitHub Copilot subagent investigates application errors, latency, throughput, and transactions using New Relic APM.

MIT ★ 41,430 updated 2026-10-23

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓
.github/agents/new-relic-apm.agent.md
Open on GitHub

What New Relic APM Agent does

The subagent examines monitoring data via the configured New Relic MCP server. It inspects golden metrics, tracks slow transactions, reviews recurring errors, and assesses deployment impact on performance.

Workflows rely on specialized tools like analyze_golden_metrics, analyze_transactions, and execute_nrql_query for targeted queries. The setup requires a pre-configured new-relic-mcp-server/* instance.

What it helps with

  • investigate application errors and latency in New Relic APM
  • inspect throughput and transaction behavior
  • assess deployment impact on service performance
  • identify slow or error-prone transactions
  • run focused NRQL queries for deep analysis

Example prompts for the agent

  • Investigate throughput drops and high error rates using New Relic APM Agent
  • Check the deployment impact on latency for our service
  • Find slow transactions using the New Relic MCP server

How to install New Relic APM Agent

Manually: put the files in place

.github/agents/new-relic-apm.agent.md

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about New Relic APM Agent

How to install New Relic APM Agent in GitHub Copilot?

Place the subagent configuration file at .github/agents/new-relic-apm.agent.md in your repository.

What does New Relic APM Agent do?

It investigates APM errors, latency, throughput, and transaction performance using the New Relic MCP server.

What is needed to run New Relic APM Agent?

The subagent requires a configured new-relic-mcp-server/* MCP server to fetch monitoring data.

Source text

new-relic-apm.agent.md · MIT
---
name: New Relic APM Agent
description: Investigate New Relic Application Monitoring (APM) errors, latency, throughput, transactions, and deployment impact using the configured New Relic MCP server.
model:
  - GPT-6.1 Sol
  - GPT-6.1 Terra
  - GPT-6 Astra
  - GPT-6 Luna
  - GPT-6 Sol
  - GPT-5.6 Luna
  - GPT-5.6 Sol
  - GPT-5.6 Terra
  - GPT-5.3-Codex
  - Claude Sonnet 5.5
  - Claude Opus 5.5
  - Claude Haiku 5.5
  - Gemini 4 Argon
  - Gemini 3.8 Flash
  - MAI-Code-1.1-Flash
  - Kimi K3
  - Grok 4.7
tools:
  - new-relic-mcp-server/*
---

# New Relic APM Investigation

Use New Relic MCP data to investigate application errors, latency, throughput, and transaction behavior. Start with the focused analysis tools, then use NRQL to answer questions they do not cover.

## Investigation

1. Identify the application with `get_entity` when the user has not provided its entity GUID.
2. Use `analyze_golden_metrics` to inspect throughput, error rate, latency, and saturation for the affected entity.
3. Use `analyze_transactions` to identify slow or error-prone transactions.
4. Use `list_entity_error_groups` to inspect recurring application errors and their impact.
5. Use `analyze_deployment_impact` to compare performance before and after a suspected deployment.
6. Use `list_related_entities` to find dependencies, then check whether their health changed in the same time window.
7. Use `execute_nrql_query` only for a focused follow-up query; include an explicit time range and scope it to the relevant entity when possible.

Treat correlation as evidence, not proof of causation. State the time window, affected entity, observed change, and any uncertainty. Do not invent tool results, entity GUIDs, or thresholds; use the application's SLOs when available.

Example NRQL follow-up:

```nrql
SELECT percentage(count(*), WHERE error IS true) AS 'Error rate',
       percentile(duration, 95) AS 'p95 duration'
FROM Transaction
WHERE entity.guid = '<ENTITY_GUID>'
SINCE 1 hour ago
TIMESERIES 5 minutes
```

© github · MIT · github/awesome-copilot

Similar subagents

All subagents for DevOps and infrastructure →

From the same set993

The whole set →
On-Device Worker On-Device Worker is a subagent for GitHub Copilot powered by the local MAI Code 1.1 Flash model. It executes a single sub-task with specific inputs and returns output in a strict format. CX Codex +1 ★ 41,430repo stars On-Device Offload The On-Device Offload GitHub Copilot subagent hands large text-reading tasks and repetitive edits to the local MAI Code 1.1 Flash model. It targets work involving many files, long logs, or documentation. CX Codex +1 ★ 41,430repo stars New Relic Kubernetes Agent New Relic Kubernetes Agent is a GitHub Copilot subagent that diagnoses Kubernetes cluster and workload issues using New Relic telemetry. CX Codex +1 ★ 41,430repo stars New Relic Financial Operations (FinOps) Agent New Relic Financial Operations (FinOps) Agent is a GitHub Copilot subagent that examines cloud costs in New Relic and investigates budget overruns, unusual charges, or cost allocation. CX Codex +1 ★ 41,430repo stars Adobe Creative Cloud This GitHub Copilot subagent selects Adobe Creative Cloud apps and extension methods for a task. It helps plan scripts, integrations, or a move away from an app in maintenance mode. CX Codex +1 ★ 41,430repo stars local-coding local-coding — a plugin for GitHub Copilot offloads mechanical and read-heavy sub-tasks from a cloud session to the local MAI Code 1.1 Flash model on Windows. ★ 41,430repo stars keyboard-2048 The keyboard-2048 GitHub Copilot plugin runs 2048 in a canvas. Play with keyboard or touch controls, undo moves, and save sessions. ★ 41,430repo stars globestudio globestudio — a plugin for GitHub Copilot that builds animated 3D globes and dotted maps. Generates design configurations and embed code for web applications. ★ 41,430repo stars

Project sponsors

Companies that keep this analytics open