Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

give names to postgresql/patroni/operator port #2247

Open
stacksegv opened this issue Feb 28, 2023 · 3 comments
Open

give names to postgresql/patroni/operator port #2247

stacksegv opened this issue Feb 28, 2023 · 3 comments
Labels

Comments

@stacksegv
Copy link

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? STACKIT Kubernetes Engine SKE
  • Are you running Postgres Operator in production? yes
  • Type of issue? feature request

We'd like to fetch the metrics provided by patroni under /metrics in the DB instance pod via prometheus. We're using the prometheus-operator and so are limited to the CRD for podMonitor or serviceMonitor to define scrape targets.
Sadly they only allow to configure scrape targets via port names not numbers. So to be able to scrape patroni metrics i'd like to add meaningful names to the ports of the postgresql-pod for patroni at least.

@thoro
Copy link

thoro commented Mar 27, 2023

I also would like to give the ports names, so I can scrape them with my prometheus multi-port config which scrapes all container ports ending in -metrics.

@FxKu FxKu added the idea label Apr 13, 2023
@stacksegv
Copy link
Author

Hey @FxKu any news on this?

abh added a commit to abh/postgres-operator that referenced this issue Sep 5, 2023
This allows them to be used in prometheus serviceMonitor or podMonitor
CRDs. Fixes zalando#2247
@abh
Copy link
Contributor

abh commented Oct 14, 2023

Planned patch in #2234

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants