![]() If you are setting up local (on-host) monitoring, use the -on-host flag. You will also need to specify an environment variable VCPASSWORD which will be the password of the PGDATABASE - the database at that address to connect to (if required for authentication) ![]() PGHOST - the address of the database to connect to PGUSER - the user with SUPERUSER or rds_superuser privileges used for setup only Note that psql will use the credentials configured in theįollowing environment variables or your ~/.pgpass file, in that order of precedence. It requires the PostgreSQL interactive terminal, psql, and privileges to access your database as Run with the -unprivileged option, the necessary monitoring functions described in the next section. The script will automatically create the required pg_stat tables,Ī user named vividcortex to be used for monitoring (with the correct privileges), and if The easiest way to prepare PostgreSQL for monitoring with DPM is by running our pg-offhost-setup shell script. ![]() Recommended: Scripted PostgreSQL Installation Pg_stat_statements please refer to the off-host installation page). Requires this privilege in order to view query text for all users. SUPERUSER/ rds_superuser is also required for remote monitoring because the pg_stat_statements extension The SUPERUSER privilege is required in order to: GRANT ALL privileges ON ALL TABLES IN SCHEMA public to rds_superuser The DPM user requires either SUPERUSER or rds_superuser (for Amazon RDS).įor non-RDS PostgreSQL, the following can be used to create a user: CREATE ROLE vividcortex SUPERUSER NOCREATEDB NOCREATEROLE INHERIT LOGIN PASSWORD '' įor PostgreSQL for Amazon RDS, you can use the following three statements: CREATE ROLE vividcortex NOCREATEDB NOCREATEROLE INHERIT LOGIN PASSWORD '' We do not use these privileges for any purpose other than running EXPLAIN. You can optionally give the DPM user INSERT, UPDATE, and DELETE privileges, which will allow DPM to run EXPLAIN on those kinds of queries. INTO OUTFILE statements, the FILE privilege is required in order to EXPLAIN REPLICATION CLIENT ON *.* is necessary to see replication failures and failure errors.SHOW VIEW is necessary for running EXPLAIN on queries which use a view.PROCESS ON *.* is necessary for running SHOW PROCESSLIST, SHOW ENGINE INNODB STATUS, andĮquivalent statements against INFORMATION_SCHEMA and PERFORMANCE_SCHEMA tables.In the case of off-host monitoring, we also need SELECT privileges to retrieve query information from the SELECT ON *.* is necessary for running EXPLAIN to capture execution plans for query samples.The following are the required privileges for MySQL: GRANT SELECT, PROCESS, SHOW VIEW, REPLICATION CLIENT ON *.* TO privileges are required for the following purposes: Require any special privileges in order to monitor): Select your database technology to view the required privileges (Redis does not The host whose credentials you want to check. You have specified by navigating to the Inventory page and clicking the ‘gear’ icon next to You must tell DPM what credentials to use to connect. This page describes the necessary privileges that user must have, along with some example statements toĬreate a user with the correct privileges. To monitor your database(s) with Database Performance Monitor, you will need to create a user for DPM to connect with.
0 Comments
Leave a Reply. |