new-relic-observability

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.

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.

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.

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.

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.

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.