Pydantic Logfire (EU region) is the EU-resident deployment of the OpenTelemetry observability platform — same surface as the US sibling row, hosted in the EU for data-residency requirements. Connect this row if your Logfire project lives at <code>logfire-eu.pydantic.dev</code>.
Why connect Logfire (EU)
EU-resident teams needing GDPR-compliant observability data residency have to keep telemetry inside the EU.
With Logfire (EU) connected, you can ask "Show me the slowest API endpoints in the last hour", "Trace count by status code today", or "Top 10 errors in the agent service" — answered against the EU-hosted Logfire project without any data leaving the region.
How the connection works
clariBI talks to Logfire (EU) through its hosted MCP server at https://logfire-eu.pydantic.dev/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 Logfire (EU)
U->>C: Click Authorize with Logfire (EU)
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 Logfire (EU) 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 Logfire (EU) cannot modify data on the vendor side.
The exact tool inventory depends on the Logfire (EU) features your account has access to. After connecting, try a few natural-language questions to see what Logfire (EU) data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Logfire (EU), 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 Logfire (EU)
U->>C: Ask a question about EU-region OpenTelemetry observability 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 Logfire (EU) card.
- Click Authorize with Logfire (EU).
- Sign in to Logfire (EU) 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
OAuth scoping is granted at authorize time. clariBI requests project:read scope. US-region customers should connect the standard logfire catalog row instead.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Project not found" | You connected the EU row but your Logfire project lives in the US region. | Disconnect this row and connect the standard logfire US row instead. |