Create a mysql, mongodb and postgresql db with scheduled backups and PITR enabled.
Create a monitoring instance. Edit the databases and enable monitoring for them.
Edit the monitoring instance, enter an invalid endpoint url
The endpoint url is accepted by the UI
The databases start restarting
Issues:
The url isn’t checked if it is valid or invalid.
Even if correct url is entered, the UI doesn’t check its username and password.
The UI doesn’t create an api key in the changed pmm url.
All existing databases using the pmm instance restart. Mysql database restarts many times and displays the error
Attaching mysql logs for analysis.
Environment
None
Attachments
4
Activity
Show:
Fábio Da Silva 4 days ago
Edited
From the FE side, there’s nothing we can do about the new URL validation. The BE should re-validate the connection based on the URL and possibly new credentials.
About checking username/password: we don’t collect those after the user inserted them the first time, that’s why there’s empty fields that are not mandatory when editing the endpoint. If users want new credentials, they can input them.
Tested with Everest v0.0.0-c25b0b1.
Create a mysql, mongodb and postgresql db with scheduled backups and PITR enabled.
Create a monitoring instance. Edit the databases and enable monitoring for them.
Edit the monitoring instance, enter an invalid endpoint url
The endpoint url is accepted by the UI
The databases start restarting
Issues:
The url isn’t checked if it is valid or invalid.
Even if correct url is entered, the UI doesn’t check its username and password.
The UI doesn’t create an api key in the changed pmm url.
All existing databases using the pmm instance restart. Mysql database restarts many times and displays the error
Attaching mysql logs for analysis.