Send OpenDunes traces to Sentry.
With the sentry destination, every OpenDunes request arrives in your Sentry project as a trace, through Sentry's OTLP endpoint.
| Setting | Required | Description |
|---|---|---|
otlpEndpoint | Yes | Your project's OTLP traces address |
dsn | Yes | Your project's DSN, https://<key>@<host>/<project id> |
A DSN of another form is a 400.
curl https://opendunes.com/v1/observability/destinations \
-H "Authorization: Bearer $OPENDUNES_MANAGEMENT_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Sentry",
"type": "sentry",
"config": {
"otlpEndpoint": "https://o123.ingest.de.sentry.io/api/456/integration/otlp/v1/traces",
"dsn": "https://abc123@o123.ingest.de.sentry.io/456"
}
}'One span per request, OTLP over HTTP at otlpEndpoint, authenticated with the key your DSN carries. The span carries the gen_ai.* attributes — the model, the provider, the token counts, the cost in DA — the input and output as text, and an error status with its message when the request failed.
Back to Broadcast overview.