MySQL User

Minimum privileges:

• SELECT ON performance_schema.*

Recommend privileges:

• SELECT, PROCESS, REPLICATION CLIENT ON *.*

For database and table sizes, Blip needs SELECT ON *.*. Although sizes are metadata, MySQL requires SELECT on an object to read its metadata.

Blip needs the PROCESS privilege to query information_schema.innodb_metrics.

Never grant ALL or SUPER privileges to the Blip MySQL user!

Password

The Blip MySQL user typically uses a password, but other authentication methods are supported too. See Monitors / MySQL Connection / Authentication.

Heartbeat

For heartbeat:

• INSERT, UPDATE, DELETE ON blip.heartbeat

Never grant write privileges to the Blip MySQL user except on the heartbeat table!

Plan Table

If using a plan table, the recommend privileges work since they grant SELECT on all tables. But if you use the minimum privileges, then the Blip MySQL also requires:

• SELECT ON blip.plans