Summary
Filtering the toolset with a request header is the same good idea Azure DevOps had, applied to observability.
An incident-response client and a reporting client want different tools from the same server, and a header lets them share one endpoint without sharing a surface. On the query side: NRQL is exactly the kind of syntax a model half-remembers, so having the translation server-side rather than in the prompt is where the reliability comes from.
What it is
New Relic's endpoint, with EU and Japan regional addresses. The headline capability is translating a plain-language question into NRQL, their query language.
What you get
- Natural language turned into NRQL queries
- Alert status checks and incident reporting
- Error log analysis for root cause
- An include-tags header that filters which tools the connection exposes
Requirements
A User API key generated in the New Relic UI, sent in an Api-Key header, or OAuth. Use the regional endpoint that matches your account.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen