New component: Prometheus Remote Write receiver

[tomatopunk]

The purpose and use-cases of the new component

The new component, Prometheus remote write receive, is designed to enable OpenTelemetry collectors to receive metrics data from Prometheus instances via the remote write protocol. This allows for seamless integration of Prometheus metrics into the OpenTelemetry ecosystem, enabling centralized metrics collection, processing, and exporting to various backends.

Example configuration for the component

receivers:
  prometheusremotewrite:
    endpoint: "0.0.0.0:12345"  # The address to listen on for Prometheus remote write 

Telemetry data types supported

metric

Is this a vendor-specific component?

• [ ] This is a vendor-specific component
• [ ] If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
• [ ] If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@tomatopunk

Sponsor (optional)

@andrzej-stencel

Additional context

The tracking issue #10358, #14751 was closed because this component did not have a sponsor.

[dashpole]

See https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/14751#issuecomment-1348879991. The lack of transactionality in PRW 1.0 makes it difficult to implement a working receiver for PRW. IMO, we should wait to introduce this until PRW 2.0, which was just released as experimental: https://prometheus.io/docs/specs/remote_write_spec_2_0/. It solves the issues raised in the previous proposal.

[ChrsMark]

Example configuration for the component

receivers:
prometheusremotewrite:
   endpoint: "0.0.0.0:12345"  # The address to listen on for Prometheus remote write 

Should we consider tls+https support as well instead of just plain http?

[andrzej-stencel]

Thanks @dashpole, this is very valuable information.

Let's make sure the new receiver supports the PRW 2.0 spec.