Database Performance Monitor supports 64-bit Linux and FreeBSD on x86 processors provided the platform meets the minimum requirements for Go:
|FreeBSD 10.3 or later||Debian GNU/kFreeBSD not supported|
|Linux 2.6.23 or later with glibc|
|CentOS 6.0 or later|
|Windows Server 2016 or later|
We also support containerized installation. Windows Subsystem for Linux (WSL) and MacOS are not supported.
For installations on a new EC2 instance to be used for monitoring (e.g. the Off-Host installation method), below are minimum recommended instance sizes. Requirements can vary slightly based on database load. If using burstable instances, be sure to choose an instance of appropriate size or enable
unlimited mode to avoid exhausting CPU credits.
|1 - 2||t3.micro||***|
|3 - 6||t3.medium||***|
|6 - 15||t3.large||15 is the maximum number of databases that can be monitored from one instance.|
|16+||n/a||Create additional instances of appropriate size.|
Versions of MySQL
DPM supports version 5.7 and above of MySQL, including MariaDB, Percona Server, and the most recent MySQL releases from Oracle. We support Amazon RDS for MySQL, Aurora for MySQL, Azure Database for MySQL, and Google Cloud SQL for MySQL using
performance_schema. Monitoring using the
performance_schema is also required when monitoring self-managed databases that use encrypted connections or Unix sockets.
When monitoring an Aurora cluster, you will need to install the agent and monitor each node as a separate instance, using the instance endpoints; do not use the general read/write endpoints.
For Google Cloud SQL for MySQL the instance tier must be at least
db-n1-highmem-4, as this is the minimum size for which Google will allow the
performance_schema to be enabled.
Versions of PostgreSQL
DPM supports all commonly used, non-EOL versions of PostgreSQL. At the time of this writing, the oldest non-EOL version of PostgreSQL is currently 10. We also support Amazon RDS and Aurora for PostgreSQL.
We support Azure PostgreSQL as well as Google Cloud SQL for PostgreSQL 11+, by using the
pg_stat_statements extension and the PostgreSQL monitoring role (
pg_stat_statements is required when monitoring self-managed databases that use encrypted connections or Unix sockets.
We support both Citus and PgBouncer. To monitor PgBouncer, DPM must be installed using the local, on-host configuration.
Versions of Redis
DPM supports Redis versions 2.0.0 and above, although versions prior to 2.6.0 will not report their full set of parameters. We do not support Redis Sentinel instances, nor managed Redis-like services such as ElastiCache.
Versions of MongoDB
DPM supports all generally available non-EOL MongoDB versions. At the time of this writing, the oldest non-EOL version of MongoDB is 4.2. We also support MongoDB Atlas, as well as self-managed MongoDB databases using encrypted connections, using either the MongoDB Profiler or the MongoDB log. DPM supports the
mongodb+srv syntax; in this case, DPM will connect to the first instance returned by DNS.
Versions of Azure SQL
DPM supports the latest generally available version of Azure SQL, including Azure SQL Database and Azure SQL Managed Instance.
Versions of SQL Server
DPM supports currently available versions of SQL Server that have not reached Microsoft’s end of support date. DPM also supports Amazon RDS for SQL Server.
We do not support Darwin (macOS), Solaris, or other non-Linux/FreeBSD platforms.