Request

Grafana Alloy wraps a lot of various Open Telemetry components, including some from the opentelemetry-collector-contrib repo (i.e. the Jaeger receiver).

This repo also has support for interacting with Datadog via OpenTelemetry, forming a receiver, connector, and exporter. While it'd be great to one day have all of these, just the exporter is necessary to have Grafana Alloy interact with Datadog today.

The exporter in v0.96.0 lacks full support for the HTTP Client settings, so if an upgrade to v0.99+ is in the near future for this repo then holding off is probably the right move as the configuration changed a bit here.

I've started working on a wrapper for the exporter library, but the documentation recommends raising an issue first before going forward with larger bodies of work.

Use case

Part of working with larger organisations is supporting a variety of tools, and being able to maintain support for Datadog telemetry (mostly traces) via Alloy enables users to maintain flexibility and slowly move their telemetry collection towards OSS.