This repository was archived by the owner on Dec 17, 2024. It is now read-only.
Unable to monitor complete DB instance #656
Unanswered
aakashmuthuramalingam
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Hello. When using the Web UI and the “DB name” field is left empty, there’s as a one time operation where all non-template DB names are fetched, prefixed with “Unique name” field value and added to monitoring (if not already monitored). Internally monitoring always happens “per DB” not “per cluster” though. I can see |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Team,
docker run -d -p 3000:3000 -p 8080:8080 -e PW2_TESTDB=true --name pw2 cybertec/pgwatch2:1.10.0
It is working fine. But I am having 3 database clusters each having 2-3 non-template databases. Even though I left the database box empty in the admin panel, still it is not giving metrics for all the DBs. only showing the metrics for Postgres database. Kindly suggest if I am missing anything. Thanks.
Expected like it will show nodeA_db1, nodeA_db2,nodeA_db3 . NodeB_db1, NodeB_db2 and so on. But it is giving database specific.
Beta Was this translation helpful? Give feedback.
All reactions