Skip to content

Promote prometheusremotewriteexporter to Stable. #39706

@ArthurSens

Description

@ArthurSens

Component(s)

exporter/prometheusremotewrite

Describe the issue you're reporting

PrometheusRemoteWriteExporter was marked as a Beta component almost 3 years ago. Ideally, the community should work towards the Stable maturity, but we never got our hands on this work. So let's get to it, better later than never.

This issue aggregates all the work we have ahead to mark the exporter as Stable, following these guidelines: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#stable

Tasks

Configuration

Following Beta's documentation, we still have room for config changes, as long as they're made through feature flags.

  • Review the current configuration, looking for fields we'd like to deprecate or required fields we'd like to add. (This task will create new issues.)

Output

Documentation

  • Review current docs, looking for gaps and improvement opportunities. (This task will create new issues.)

Resiliency

  • Experiment with ordered WAL implementations
  • Review component's observability. (This task will create new issues.)
    • Review throughput metrics
    • Review latency metrics
    • Review data drop metrics
    • Review correctness metrics
    • Review performance metrics/spans
    • Review error handling logs

Maintainability

Specification alignment

  • Update otel<->remote-write specification with Prometheus's UTF-8 changes.
  • Update otel<->remote-write specification with Prometheus's Native Histograms
  • Work with Prometheus' PRWv2 and Delta working groups to verify the possibility of Delta support.
  • Review the impact that prometheus/proposals#39 might cause in the Remote Write exporter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions