Skip to main content
This feature is in early access and behind a feature flag. Contact your Augment Solutions Architect to enable it for your tenant
Cosmos has a guided form for each provider below. Pick it after Add Destination, or paste the provider’s endpoint URL into the search box to open its form with the region filled in. The form builds the traces URL and headers shown here. For any other OTLP/HTTP endpoint, use Custom OTLP. See Set up Trace Export. In the tables:
  • {…} is a value you pick or paste in the form.
  • Signals lists what the provider accepts besides traces. Where it says traces only, the provider has no OTLP metrics or logs endpoint next to its traces endpoint, so Send metrics and Send logs are unavailable.
  • Header values marked secret are write-only after you save.

Summary

APM and observability

Datadog

Grafana Cloud

An HTTP 530 from Grafana Cloud usually means the zone is wrong. Copy it from your stack’s OTLP endpoint.

Honeycomb

New Relic

Dynatrace

Splunk Observability

Elastic Observability

Dash0

Coralogix

SigNoz

Axiom

Sentry

PostHog

AI and LLM observability

Langfuse

LangSmith

Braintrust

Arize AX

Weave

W&B Weave, by Weights & Biases.

Comet Opik

Pydantic Logfire

Databricks

Snowflake

Cloud

AWS X-Ray

For providers with regions, keys usually work only in the region they were created in. If a test fails with HTTP 401 or 403, check that the region in the form matches the key’s region.

Your own collector

Use Custom OTLP to send to an OpenTelemetry Collector that you run, then route from it to any backend, including ones Cosmos can’t reach directly. Expose the collector’s OTLP/HTTP receiver at a public HTTPS URL and protect it with a header the collector checks, for example with the bearer token auth extension.
In Cosmos, set Traces URL to the collector’s public URL ending in /v1/traces, and add the header Authorization: Bearer <token>.