You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
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.
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 ?
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!
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!
Questions
I can set up postgres-exporter via
monitoring -> pgmonitor -> exporter
in postgres-operator v5.5But like
ccp_stat_user_tables
metrics, only collect metrics frompostgres
databaseShould I set up the another postgres-exporter in sidecar ?
This is the same issue
The text was updated successfully, but these errors were encountered: