Skip to content

PrometheusReceiver Configuration - Deprecate ReportExtraScrapeMetrics #44181

@ArthurSens

Description

@ArthurSens

Component(s)

receiver/prometheus

Describe the issue you're reporting

When enabled, extra metrics that bring information about the scrape will be included. This is an option because such behavior is considered an experimental feature in Prometheus.

As noted in a related issue (#44196), a Stable component needs to be observable by default, and several important metrics related to the scrape behavior are only available if ReportExtraScrapeMetrics is set to true. That sparks the question: Should this be false by defalt? Should this even be configurable?

The reason why it's configurable today is because the feature itself is considered experimental in Prometheus upstream, and might be removed without prior notice.

This issue is being created to start discussion on how to proceed. Should we work with Prometheus upstream to stabilize this feature? Should we keep things as they are?

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Workable

    Status

    Workable

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions