Closed laurencefass closed 1 year ago
Hello.
According to the manual:
one can also deploy the pgwatch2 gatherer daemons more easily in a de-centralized way, by specifying monitoring configuration via YAML files. In that case there is no need for a central Postgres “config DB”.
That means one cannot use YAML config file and Postgres config database simultaneously. Since web UI is a frontend for a config database there is no possibility to use it as well.
The straightforward solution might be to update YAML configuration manually and force pgwatch2 to reread it.
I am trying to load an instance using config.yaml. Not only does defining an instance with PW2_CONFIG not work, but it prevents me from manually entering and instance with the exact same details through the UI.
Summary:
These are my settings.
docker-compose.yml
i'm running these pg queries on the database after bootstrapping which enables monitoring only if I excluded PW2_CONFIG and I define my instance manually in the UI
config.yaml (based on this template - Ive tried to disable as much as possible)