DBMS uptime

Job details

Parameters

Job Summary

• Purpose: The purpose of this job is to collect uptime statistics for the MySQL instance. It monitors the uptime of the MySQL instance and tracks when the database is started and last checked. This information assists in finding patterns in downtime or restart frequency, and allows a snapshot of current uptime statistics.
• Why: This thorough monitoring and data tracking enables the prediction and understanding of downtime patterns, providing crucial information for maintaining and improving the availability of the database.
• Manual checking: You can check this manually in the database by issuing SQL commands found within the “implementation” and “post-implementation” sections of the XML content.

Dependencies

Several dependencies are present, including:

• Current statistics (“dbw_dbms_uptime_data”)
• Main procedure (“dbw_dbms_uptime”)
• A table (“dbw_dbms_uptime_histr”) and several supporting views (“dbv_dbms_uptime_histr”, “dbv_dbms_monitored” and others)
• Base views (“dbv_dbms_availability”, “dbv_dbms_uptime_stat” and “dbv_dbms_uptime_stat_h”)

In the event of failure, the job will clean up all dependencies.

Procedures & Views

The job creates tables, procedures and views in the implementation section, using SQL commands. It creates tables for data and history, a procedure to collect and update uptime data, and several views to extract and calculate uptime information.

Report

The job generates a report titled “DBMS Uptime”, providing uptime statistics and indicating periods when the database was up. The presentations in the report include:

• Availability statistics: DBMS uptime, monitored time, down time, and uptime as a percentage.
• DBMS uptime periods: Details on DBMS startup, last sampled date, days up and the period span.

Post-Implementation

After the main implementation, the job alters the initially created views with updated queries in the post-implementation section, leading to more precise views in relation with uptime history, monitored days, stopped days, up days and availability.

Upgrade

An upgrade path is included for version “1.0″ and version “2.3″ to the current version of the job. During the upgrade, the job will drop the existing “dbw_dbms_uptime” procedure and create a new one.

Installation & Other Info

The job has been designed for easy, automatic installation, signified by the “express-install” and “force-install” elements. It specifically targets instances which are MySQL branch, has an engine available, can use global variables information schema, and has a major version greater than ‘5.5′. Its metadata places it in the “Availability” category.