New Relic watches the health of applications and infrastructure: response times, error rates, throughput, and the alerts that fire when something breaks. Connecting New Relic to clariBI brings that operational signal into the same analyses as your revenue and product data, so a reliability question gets answered next to a business one.
Why connect New Relic
Reliability data usually lives in a dashboard only the on-call engineer opens. Pulling it next to business metrics means manual exports that go stale within a day.
With New Relic connected, you can ask "Which services threw the most errors during last week's checkout outage?", "Compare API latency before and after the Tuesday release", or "How many alerts fired per service this month?" and the AI engine reads the answer live.
How the connection works
clariBI talks to New Relic through its hosted MCP server at https://mcp.newrelic.com/mcp. Authentication uses an OAuth flow that clariBI registers itself for (no developer console setup on your side). Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as New Relic
U->>C: Click Authorize with New Relic
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only New Relic tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting New Relic cannot modify data on the vendor side.
The exact tool inventory depends on the New Relic features your account has access to. After connecting, try a few natural-language questions to see what New Relic data clariBI can pull.
Data flow during analysis
When you ask a question that maps to New Relic, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as New Relic
U->>C: Ask a question about observability and application performance data
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the New Relic card.
- Click Authorize with New Relic.
- Sign in to New Relic in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
clariBI connects through New Relic's OAuth flow and inherits the connected user's account access. The catalog exposes read tools only (querying entities, metrics, and alert state); nothing in New Relic is changed. Disconnect anytime from Settings → Integrations in clariBI, or revoke the grant from your New Relic account.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "No data returned for a service" | The connected New Relic account cannot see that entity, or the service reports under a different name. | Confirm the service name in New Relic and that your user has access to the account or sub-account it reports under. |
| "Authorization expired" | The OAuth grant timed out or was revoked in New Relic. | Reconnect from Settings → Integrations; clariBI re-runs the one-click authorization. |