Skip to content

Monitoring TokuMX

Leif Walsh edited this page May 5, 2014 · 1 revision

Monitoring TokuMX

A database administrator needs to have a good understanding of how a database uses system resources.  This information is useful for capacity planning, performance tuning, and incident diagnostics.

In addition, any database needs to be monitored, to identify and diagnose problems on both long (performance) and short (errors) time scales.

Optimal administration of a database system essentially requires an understanding of three things:

  1. How the database is expected to use system resources under a given workload.
  2. Where the database reports internal metrics and what they mean.
  3. How to collect and interpret both system and internal database metrics.

This section contains information on each of these aspects of monitoring a TokuMX database. Some of the information here would be relevant to any database system, some is specific to TokuMX. It's best to read each of these documents in order, skipping those that are irrelevant for your use case (e.g. sections on sharding can be ignored if you don't use sharding).

Clone this wiki locally