new-relic-observability

Access New Relic observability tools through an APIM proxy with Entra ID authentication.

Updated Jun 2, 2026

Search Tags:#Azure #APIM #Observability #New Relic #Incident investigation

Ready to run

npx skills add https://github.com/AMNEngineering/newrelic-mcp-apim --skill new-relic-observability-amnengineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-relic-observability
Source: https://github.com/AMNEngineering/newrelic-mcp-apim/tree/main/skill
Command: npx skills add https://github.com/AMNEngineering/newrelic-mcp-apim --skill new-relic-observability-amnengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires az, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines access to New Relic observability tools, eliminating the need for direct API keys on developer machines and centralizing key management with a secure APIM proxy.

Core Features & Use Cases

Centralized API Key Management: APIM manages the New Relic API key, eliminating the need for developers to store keys on their machines.
Entra ID Authentication: Developers authenticate with Azure AD, simplifying the access control process.
Rate Limiting: Protects against excessive usage with a 300 calls/minute rate limit.
Single Source of Truth: APIM injects the NR API key into all requests, ensuring consistency.
Use Case: Ideal for incident investigation, deployment validation, and monitoring alert conditions in New Relic.

Quick Start

Use the new-relic-observability skill to list the available capabilities in New Relic.

Frequently Asked Questions about new-relic-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I secure New Relic API keys for incident investigation without storing them locally?▼

You can secure New Relic API keys by routing observability requests through an Azure APIM proxy. APIM centrally manages and injects the API key into requests, eliminating the need for developers to store keys on their local machines.

What authentication is required to access New Relic observability tools through an APIM proxy?▼

Accessing New Relic observability tools through an APIM proxy requires Entra ID authentication. Developers must authenticate using Azure AD, and Azure CLI is required to acquire the necessary access tokens.

How does rate limiting work when monitoring New Relic alert conditions via APIM?▼

Rate limiting for New Relic monitoring via APIM is configured to protect against excessive usage by enforcing a limit of 300 calls per minute. This ensures consistent and controlled access to the observability API.

Can I use Azure CLI to validate deployments and monitor alerts in New Relic?▼

Yes, you can use Azure CLI to acquire authentication tokens for Entra ID, allowing you to validate deployments and monitor alert conditions in New Relic securely through the centralized APIM proxy.

What are the limitations of using an APIM proxy for New Relic observability access?▼

The primary limitation of using an APIM proxy for New Relic access is a strict rate limit of 300 calls per minute, and it requires Azure CLI for token acquisition, which may restrict automated high-volume querying.

Is centralized API key management through APIM the best way to handle New Relic access control?▼

Centralized API key management through APIM is highly effective for New Relic access control because it establishes a single source of truth, injects keys automatically, and enforces Entra ID authentication.