Watchdog Alarm Summary Report

Author: Sophie Renshaw

On both Crown Castle and ExteNet we have the Watchdog Alarm Summary Report. It is hidden to the customer but lets us see what watchdogs have not cleared on the relevant servers.

As part of the support process whoever is on Level 2 (Watchdog Rota) in the morning should be running the report for both customers to check for any watchdogs that haven’t cleared. If there are any on either report they need to be investigated and reported to ensure that they don’t become service impacting.

The report is a very simple report and it uses a number of database profiles in the reporting manager along with a MySQL query to return information on the Watchdogs.

For Example: Crown Castle Production

Database connections are declared:

• Each of these connections has their own Database Profile in the reporting Manager

• In this profile the name, connection URL, user name, password and Driver must be specified
• It might be necessary to grant privileges on the server for the username/IP address combo that is being used:

   GRANT SELECT ON *.* TO 'reader'@'yourIpAddress' identified by 'password';

• Note: Try to give as little permission as possible to the profile to still allow it to perform as expected.

• Changing the report to add another server into monitoring:
  1. Add the Database connection
  2. Create the Database Profile
  3. Ensure the profile has access
  4. Test and Monitor for Watchdog alarms.