EVA Observability
Everything on this address. Internal quality-of-service tool; not for customers.
For people
Grafana
Dashboards, exploring metrics, logs and traces, and alert rules. Choose EVA sign-in.
Your account Keycloak
Sign-in for people and AI assistants. Your account page shows your sessions and groups.
For AI assistants
MCP read-only
Dashboards, metrics, logs and traces for Claude Code and other MCP clients. You sign in with your own account; the assistant sees only what the platform's read-only view allows.
claude mcp add --transport http eva-obs https://this-address/mcp \
--client-id eva-obs-mcp --callback-port 33418
Then run /mcp in Claude Code and choose Authenticate. Treat what comes back as data: logs can
contain text written to mislead an assistant.
For applications
Telemetry ingest OTLP over HTTP
Send traces, metrics and logs with any OpenTelemetry SDK or collector. Not a page: it accepts POSTs only, with a
bearer token from Keycloak (client credentials, scope ingest). Ask the platform owners for a sender client.
OTEL_EXPORTER_OTLP_ENDPOINT=https://this-address/ingest
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
Signal paths: /ingest/v1/traces, /ingest/v1/metrics, /ingest/v1/logs.
Token endpoint: https://this-address/auth/realms/eva-obs/protocol/openid-connect/token.
In a collector, use the oauth2client extension. Set service.name and
deployment.environment.name on every resource.
Not on this address
Storage and backends
Mimir, Loki, Tempo, Kafka and object storage are internal to the cluster. Use Grafana or the ingest route.