Monitored technologies · Databases

MySQL Monitoring

MySQL server, connections, caches and index usage under continuous monitoring, with checks adapted to the environment in which the database operates.

From the key metrics to troubleshooting

MySQL is the most widely used open source relational database system: its performance and ease of use make it one of the pillars of the market. It consists of a server part and a client part, both available on Unix and Windows systems.

The Sentinet³ MySQL Pattern monitors both components with checks customised to the environment in which the database operates, performs continuous monitoring and flags potential problems before they hit the system. The checks start from the most important metrics, the ideal starting point for troubleshooting.

At a glance
PatternSentinet³ MySQL Pattern
SourcesDirect authenticated access to the database
ScopeServer, connections and activity, caches, indexes and queries
Sentinet³ Enterprise Console: hosts grouped with their services and the host and service status counters
Sentinet³ console: host and service status.
What it checks

The Pattern’s checks

The Pattern includes 20 checks. Each has configurable thresholds and generates a notification when values exceed them.

Server

CheckWhat it verifies
ReachabilityThe server responds on the network
CPUPercentage of CPU utilisation
MemoryMemory usage
DiskFree disk space
ServiceService availability

Connections and activity

CheckWhat it verifies
Connection TimeTime to connect to the database
UptimeMinutes of database activity
Long running procProcesses that have been running for a long time
Threads connectedNumber of open connections

Cache

CheckWhat it verifies
Query cache hit rateQuery cache hit rate
Thread cache hit rateThread cache hit rate
Buffer pool hit rateInnoDB buffer pool hit rate
Buffer pool wait freeInnoDB buffer pool waits for a free page
Key cache hit rateMyISAM key cache hit rate
Table cache hit rateTable cache hit rate
Log waitsWaits caused by log buffer capacity
Query cache low mem prunesEntries removed from the query cache due to insufficient memory

Other

CheckWhat it verifies
Index usagePercentage of index usage
Slow queriesFrequency of queries detected as slow
Temp disk tablePercentage of temporary tables created on disk instead of in memory
Why it matters

Data read correctly, policies respected

  • Authenticated access: Sentinet³ queries MySQL databases by accessing the system directly with authentication: data is read correctly according to the user level employed, in compliance with company policies.
  • Server and client: both MySQL components are monitored, on Unix and Windows alike.
  • Prevention: continuous monitoring flags potential problems before they hit the system.

Want to see Sentinet³ on your infrastructure?

Tell us about your environment: sites, technologies, critical services. We will show you how Core and Infinity can work on your case.