All integrations

Oodle

Instrumentation

Send agent traces to Oodle over OpenTelemetry.

Read the full instrumentation docs

Install

Add Oodle instrumentation from eve's registry. Oodle ingests OTLP directly:

bash
eve add instrumentation/oodle

Quick start

Create agent/instrumentation/oodle.ts and send traces to Oodle's OTLP endpoint with your API key and instance ID:

ts
// agent/instrumentation/oodle.tsimport { OTLPHttpProtoTraceExporter } from "@vercel/otel";import { otelIntegration } from "eve/instrumentation/otel";
export default otelIntegration({  exportPolicy: {    span: () => ({ redact: true, inputs: true, outputs: true }),  },  traceExporter: new OTLPHttpProtoTraceExporter({    url: `https://${process.env.OODLE_OTLP_ENDPOINT}/v1/traces`,    headers: {      "X-API-KEY": process.env.OODLE_API_KEY!,      "X-OODLE-INSTANCE": process.env.OODLE_INSTANCE!,    },  }),});

Configure

Open Oodle’s eve integration tile to get your OTLP collector domain, API key, and instance ID. Set OODLE_OTLP_ENDPOINT to the domain only, without a scheme or path; the template adds https:// and /v1/traces. Set OODLE_API_KEY and OODLE_INSTANCE to the supplied values. The registry template redacts inputs and outputs before export. See Oodle’s eve guide for Oodle setup and the OpenTelemetry guide for trace topology and content policy.