MySQL

opsverse's can be used to collect metrics from mysql dbs you can also install the https //docs opsverse io/amazon rds on a single machine if you're running mysql db on rds kubernetes add the following yaml snippet to the agent's values yaml and run the agent based on these https //docs opsverse io/install the opsverse agent#veqxm mysql exporter enabled true \# # set a name for this db will be used in dashboards and annotations podlabels db name "your db name" \# # not recommended for production usage \# # for production, define a secret with the data source url as the key \# # see the example provided in the file mysql host \<connection url> pass \<password> user \<username> \# for production \# existingsecret mysql secret name \# the secret should be of this format \# key data source url \# value base64 encoded value of username\ password@(mysql host\ post)/ \# apiversion v1 \# data \# data source name \<base64 encoded string> \# kind secret \# name mysqld exporter prometheus mysql exporter \# namespace default single machine alternatively, you can install the https //github com/prometheus/mysqld exporter on a single machine prerequisite(s) you have the https //docs opsverse io/install the opsverse agent#veqxm https //github com/prometheus/mysqld exporter#required grants on db are enabled run this command to install the mysql exporter as a systemd unit \# for amd64 curl https //raw\ githubusercontent com/opsverseio/installers/main/prometheus exporters/install exporter amd64 sh | sudo bash s e mysqld \# for arm64 curl https //raw\ githubusercontent com/opsverseio/installers/main/prometheus exporters/install exporter arm64 sh | sudo bash s e mysqld the agent will begin scraping the metrics automatically; the script will drop the scrape target into /etc/opsverse/targets/ , so the agent will begin automatically scraping if you need to update mysql connection info , after you install, you may edit /etc/opsverse/exporters/mysqld/ my cnf and then restart the service sudo systemctl restart prom mysqld exporter