Database Monitoring Setup

Database Monitoring shows what your databases are doing at the query level: which queries run most often, which are slow, what they wait on, and which application services send them. The Middleware Agent collects this data through your database integration, so each database needs a short one-time setup before its queries appear under APM → Database.

New to Database Monitoring? Start with these three.

One setup per database server.

Install the agentOn a host or Kubernetes cluster that can reach your database
Prepare your databaseCreate a monitoring user and turn on the data collection your engine needs
Open APM → DatabaseInstances, query metrics and samples appear once traffic flows

Choose your database#

Pick the engine you run. Each guide covers the database-side settings, the monitoring user, and the collection options to turn on in the integration.

Supported engines for query-level monitoring.

PostgreSQLEnable pg_stat_statements, create a monitoring user, and turn on query sample, top query and schema collection.

MongoDBCreate a profiling user and set the profiling level so slow operations appear in Query Metrics and Samples.

Explore your database data

Once your database is set up, these are the places to go next.

Database MonitoringQuery metrics, samples, explain plans, wait events and schemas.Install the AgentThe agent collects database data, so it must be able to reach the database.Database IntegrationsConnection and TLS options for every supported database integration.

Need assistance or want to learn more about Middleware? Get in touch with us via our Contact Us or join our Slack channel.

What did you think of this content?