Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.idun-group.com/llms.txt

Use this file to discover all available pages before exploring further.

Idun Engine includes built-in observability backed by OpenTelemetry auto-instrumentation. It captures traces, logs, and metrics from your agents with minimal configuration. The standalone runtime always captures traces locally into its own DB-backed trace store. External providers (Langfuse, Phoenix, LangSmith, GCP Trace) stack on top: configure one or more in the admin panel or config.yaml, and the engine fans spans out to local storage and every enabled provider.

​
Supported providers

​
How it works

When you attach an observability configuration to an agent, the platform automatically instruments the agent runtime. Depending on the provider, you get:
  • Traces showing agent execution flow, LLM calls, and tool invocations
  • Latency metrics for each step in the agent graph
  • Cost tracking based on token usage
  • Error traces with full context for debugging
  • Structured logs for centralized log analysis

​
Configuration

Add an observability section to your config.yaml with the provider and its credentials:
config.yaml
observability:
  - provider: "LANGFUSE"
    enabled: true
    config:
      public_key: "pk-lf-..."
      secret_key: "sk-lf-..."
      host: "https://cloud.langfuse.com"
The observability key is a list, and you can attach more than one provider at a time; each entry is lazy-loaded and the engine fans spans out to every enabled provider. See the provider-specific pages for the full list of fields each provider requires.

​
Probing the connection programmatically

The configured observability provider can be smoke-tested without going through the admin UI. POST /admin/api/v1/observability/check-connection runs the same probe the admin Test-connection button uses and returns a StandaloneConnectionCheck: 
curl -sX POST http://localhost:8000/admin/api/v1/observability/check-connection \
  --cookie "$IDUN_SESSION_COOKIE"
Langfuse, Phoenix, and LangSmith providers get an HTTP HEAD (falling back to GET on >= 400) against their configured endpoint; success means an HTTP status under 500: 
{
  "ok": true,
  "details": { "provider": "LANGFUSE", "host": "https://cloud.langfuse.com", "status": 200 },
  "error": null
}
GCP_TRACE and GCP_LOGGING return ok: true with a details.note flagging that the runtime auth check needs GCP credentials and was not attempted; the probe only validates that project_id is set: 
{
  "ok": true,
  "details": {
    "provider": "GCP_TRACE",
    "projectId": "my-project",
    "note": "config valid; runtime auth check requires GCP credentials"
  },
  "error": null
}
The probe returns HTTP 404 when no provider is configured. Otherwise every outcome is HTTP 200 with ok reflecting reachability, runs under a 5-second timeout, and never raises (services/connection_checks.py). The route is admin-authenticated: under IDUN_ADMIN_AUTH_MODE=password you need the session cookie minted by POST /admin/api/v1/auth/login. Use this in pre-deploy gates to confirm credentials still resolve before flipping traffic.

​
Next steps

Local traces

Browse, search, and inspect AG-UI run events captured by the standalone’s trace store.

Telemetry events

The OpenTelemetry event shape the engine emits.

Custom handler

Wire your own span handler when the built-in providers don’t fit.
Last modified on May 26, 2026