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

How to collect non postgres database metrics via pgmonitor #3829

Open
KennyChenFight opened this issue Jan 23, 2024 · 4 comments
Open

How to collect non postgres database metrics via pgmonitor #3829

KennyChenFight opened this issue Jan 23, 2024 · 4 comments

Comments

@KennyChenFight
Copy link

KennyChenFight commented Jan 23, 2024

Questions

I can set up postgres-exporter via monitoring -> pgmonitor -> exporter in postgres-operator v5.5
But like ccp_stat_user_tables metrics, only collect metrics from postgres database
Should I set up the another postgres-exporter in sidecar ?

This is the same issue

@dsessler7
Copy link
Contributor

Hello @KennyChenFight,

The global metrics that are collected by the exporter are collected from all databases. However, you are correct that we don't currently have per-db type metrics. That being said, this is a feature that we have in our development backlog.

@KennyChenFight
Copy link
Author

KennyChenFight commented Jan 24, 2024

Hello @KennyChenFight,

The global metrics that are collected by the exporter are collected from all databases. However, you are correct that we don't currently have per-db type metrics. That being said, this is a feature that we have in our development backlog.

@dsessler7
Thank you for your reply. So the current workaround way is that we set up another postgres-exporter in another deployment or in pgo sidecar and change DATA_SOURCE_URI env to collect another database metrics ?

@dsessler7
Copy link
Contributor

dsessler7 commented Jan 26, 2024

We don't have a documented "workaround" since this is more of a new feature than a bug, but what you've suggested there definitely sounds like you're on the right track. If you give it a try we'd love to hear how it goes/what you find out!

@KennyChenFight
Copy link
Author

We don't have a documented "workaround" since this is more of a new feature than a bug, but what you've suggested there definitely sounds like you're on the right track. If you give it a try we'd love to hear how it goes/what you find out!

Got it. And thanks for your reply 😃

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

No branches or pull requests

2 participants