Skip to content

Conversation

bitglue
Copy link
Contributor

@bitglue bitglue commented Oct 18, 2018

When using --disable-default-metrics, I expect postgres_exporter to
provide no metrics besides those explicitly requested with
--extend.query-path.

See #168 (comment)

When using --disable-default-metrics, I expect postgres_exporter to
provide _no_ metrics besides those explicitly requested with
--extend.query-path.

See prometheus-community#168 (comment)
@coveralls
Copy link

coveralls commented Oct 18, 2018

Coverage Status

Coverage increased (+0.1%) to 58.69% when pulling 47be079 on bitglue:disable_default_settings_query into 72446a5 on wrouesnel:master.

@bitglue
Copy link
Contributor Author

bitglue commented Oct 18, 2018

I just saw a similar thing has already implemented in #223. My preference would be to not introduce a new flag: the common use cases I can think of involve either wanting all the default metrics, or none of them. No reason to treat settings specially.

@wrouesnel
Copy link
Contributor

I agree @bitglue on this - I can't see a reason to make this super-granular (Prometheus can be configured to drop metrics anyway).

@brosander
Copy link

We've set up an autobuild that builds v0.4.7 with this pr cherry picked on top:

corvana/postgres-exporter:v0.4.7-no-pg-settings

This is required for us to be able to scrape greenplum.

@wrouesnel
Copy link
Contributor

This feature is introduced by #215 is now merged to master.

@wrouesnel wrouesnel closed this Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants