Observagent
Agent integration · Windows · macOS · Linux

Connect Devin to Observagent.

Export Devin agent session telemetry over OpenTelemetry, using either standard OTLP environment variables or Devin's otel configuration block.

Select OS Review data sent
DevinAgent session events
OTLP over HTTPSHTTP/protobuf
ObservagentLogs + metrics
How it works

Use Devin's OpenTelemetry export

Devin can export agent events and timing metrics to an OpenTelemetry collector, either through the standard OTEL_EXPORTER_OTLP_* environment variables that most OpenTelemetry SDKs recognize, or through an otel block in Devin's own user configuration. Observagent accepts either path over OTLP/HTTP.

  • This covers Devin's own session and step telemetry, not the separate REST API or Jira/Linear webhook triggers Devin also supports for starting sessions.
  • Devin is under active development; exact config keys and available event fields can change between releases.
  • Telemetry begins after configuration and a restart; existing sessions are not backfilled.
Before you begin

Minimum required plan

Not confirmed for external OTLP export.

  • Devin Free is the minimum for limited product usage. This does not establish eligibility for the external OTLP integration described here.
  • We have not verified a minimum plan or exporter support for this integration. A Free, Pro, or Enterprise account must not be treated as confirmed OTLP access.
Observagent accessPrepare an Observagent project with monitoring and the required signals enabled, plus a valid project key with telemetry:write permission.

Requirements reviewed on .

Select OS

Integration steps

Select a platform to see commands and paths for your computer. Project setup and delivery verification are shared across platforms.

WindowsPowerShell
  1. Step 1

    Create a project and project key

    In Observagent, enable Logs and Metrics on a project, turn monitoring on, and generate a project key with telemetry:write permission.

    • Use a separate key for Devin so Observagent can attribute this source reliably.
  2. Step 2

    Configure the OTLP exporter

    Set the standard OTLP environment variables in the shell that launches Devin, or use the equivalent otel block in Devin's own config file if your installed version reads one.

    • These are the standard OTEL_EXPORTER_OTLP_* variables most OpenTelemetry SDKs recognize.
    • If your Devin version reads an otel block from its own config file instead, use these same values there.
    PowerShell
    $env:OTEL_EXPORTER_OTLP_ENDPOINT = "https://dashboard.observagent.cloud"
$env:OTEL_EXPORTER_OTLP_HEADERS = "Authorization=Bearer YOUR_PROJECT_KEY"
$env:OTEL_EXPORTER_OTLP_PROTOCOL = "http/protobuf"
  3. Step 3

    Restart Devin and verify delivery

    Fully restart the Devin session or CLI process, run a task that reaches at least one tool call, then check Logs and Metrics for the project in Observagent.

    • Restarting is required so Devin picks up the new environment or config values.
    • Telemetry starts with new activity after configuration and does not backfill earlier sessions.
Troubleshooting

Diagnose exporter failures

  • Nothing arrives: confirm the variables (or config block) are present in the exact process that runs Devin, and that the session was restarted after the change.
  • 401/403 from Observagent: the bearer header is missing, malformed, revoked, or lacks telemetry:write.
  • Config not recognized: the otel block schema is representative; check Devin's current changelog and configuration reference for the exact keys your version expects.
  • Only session lifecycle events arrive: confirm the task actually reached a tool call or model request, not only session start.
  • Old sessions are missing: telemetry starts with new activity after configuration and does not backfill history.
Privacy

Review what gets exported

Treat Devin's OpenTelemetry export as operational session and timing telemetry, not a guaranteed prompt-free feed. Review Devin's current documentation for exactly which fields it includes before enabling this for sessions that touch sensitive repositories or data. Observagent applies its own server-side content controls as an additional boundary.