Skip to main content

New Relic APM Agent

Investigate New Relic Application Monitoring (APM) errors, latency, throughput, transactions, and deployment impact using the configured New Relic MCP server.

Install

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:

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