mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-08 08:25:09 +00:00
fa89ac428e
Adds a consolidated `datadog.mdx` under `docs/edge/{en,pt-BR,ko,ar}/enterprise/guides/`
covering both the Datadog Agent path (stdout JSON logs via `CREWAI_LOG_FORMAT=json`)
and the Datadog OTLP intake, with a JSON log schema reference and a ready-to-import
operations dashboard (`datadog_dashboard.json`). Reframes `capture_telemetry_logs.mdx`
to lead with OpenTelemetry as the vendor-neutral path and point readers to the new
Datadog page for that ecosystem's setup.
58 lines
3.0 KiB
Plaintext
58 lines
3.0 KiB
Plaintext
---
|
|
title: "OpenTelemetry Export"
|
|
description: "Export traces and logs from your CrewAI AMP deployments to your own OpenTelemetry collector"
|
|
icon: "magnifying-glass-chart"
|
|
mode: "wide"
|
|
---
|
|
|
|
CrewAI AMP can export OpenTelemetry **traces** and **logs** from your deployments directly to your own collector. This lets you monitor agent performance, track LLM calls, and debug issues using your existing observability stack.
|
|
|
|
Telemetry data follows the [OpenTelemetry GenAI semantic conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/) plus additional CrewAI-specific attributes.
|
|
|
|
<Tip>
|
|
OpenTelemetry is the **recommended observability path** — vendor-neutral, works with any OTLP-compatible backend (Grafana, Honeycomb, NewRelic, your own collector). If you specifically use Datadog, see the dedicated [Datadog Integration](./datadog) guide which covers both the Datadog Agent path and Datadog's OTLP intake.
|
|
</Tip>
|
|
|
|
## Prerequisites
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="CrewAI AMP account" icon="users">
|
|
Your organization must have an active CrewAI AMP account.
|
|
</Card>
|
|
<Card title="OpenTelemetry collector" icon="server">
|
|
You need an OpenTelemetry-compatible collector endpoint (e.g., your own OTel Collector, Datadog, Grafana, or any OTLP-compatible backend).
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## Setting up a collector
|
|
|
|
1. In CrewAI AMP, go to **Settings** > **OpenTelemetry Collectors**.
|
|
2. Click **Add Collector**.
|
|
3. Select an integration:
|
|
- **OpenTelemetry Traces** and **OpenTelemetry Logs** — export to any OTLP-compatible collector or backend.
|
|
- **Datadog** — send traces straight to Datadog's OTLP intake, no separate collector or Datadog Agent required.
|
|
4. Configure the connection. The fields depend on the integration you selected:
|
|
|
|
<Tabs>
|
|
<Tab title="OpenTelemetry Traces / Logs">
|
|
**OpenTelemetry Traces** and **OpenTelemetry Logs** are separate integrations that share the same fields — pick the one matching the signal you want to export.
|
|
|
|
- **Endpoint** — Your collector's OTLP endpoint (e.g., `https://otel-collector.example.com:4317`).
|
|
- **Service Name** — A name to identify this service in your observability platform.
|
|
- **Custom Headers** *(optional)* — Add authentication or routing headers as key-value pairs.
|
|
- **Certificate** *(optional)* — Provide a TLS certificate if your collector requires one.
|
|
|
|
<Frame></Frame>
|
|
</Tab>
|
|
<Tab title="Datadog">
|
|
For Datadog setup, see the dedicated [Datadog Integration](./datadog) guide — it covers both the Datadog Agent path (recommended, cheaper for log volume) and Datadog's OTLP intake with full collector configuration steps.
|
|
</Tab>
|
|
</Tabs>
|
|
|
|
5. *(optional)* Click **Test Connection** to verify CrewAI can reach the endpoint with the credentials you provided.
|
|
6. Click **Save**.
|
|
|
|
<Tip>
|
|
You can add multiple collectors — for example, one for traces and another for logs, or send to different backends for different purposes.
|
|
</Tip>
|