System Up Time Monitoring

Introduction to the System Up Time Monitoring Management Pack for Operations Manager 2007

The System Up Time Monitoring Management Pack leverages the Windows ‘System Up Time’ performance counter and is designed to help System Administrators with monitoring and reporting on planned and unplanned system reboots.

The System Up Time Monitoring Management Pack augments both the Windows Server Operating System Management Pack for Operations Manager 2007 and the
Windows Client 2000/XP/Vista Operating System Management Pack for Operations Manager 2007.

Three example scenarios are:

  1. Run the System Up Time Report against a group of servers to validate they cycled as part of the required emergency security patch requiring a reboot.
  2. Run the System Up Time Compliance Report against the ‘All Windows Computers’ group to show all computers not rebooting according to their daily, weekly, monthly, or quarterly reboot schedule.
  3. Enable the System Uptime Weekly Reboot Monitor and receive an alert for a critical front end application server that didn’t complete a required system reboot after its backend system IPL completes on Sundays.

Document Version

This guide is based on the June 2010 System Up Time Monitoring Management Pack. Version 1.0.0.17
Supported Configurations

The System Up Time Monitoring Management Pack for Operations Manager 2007 is designed to monitor Windows Computers only and requires the prerequisite discovery of the Windows Computer base class.

The System Up Time Monitoring Management Pack supports all of the Windows platforms supported by System Operations Manager 2007 R2.

Getting Started

This section describes the actions you should take before you import the management pack, any steps you should take after you import the management pack, and information about customizations.
Note: All System Uptime Reboot Monitors are disabled by default. To enable Monitoring, please use overrides to enable monitoring for the systems desired.

Files to Download
To monitor System Up Time, you must first download the System Up Time Monitoring Management Pack. The System Up Time Monitoring Management Pack includes the files described in the following table. (Ideally, this MP should be sealed)

Filename Description
System.Uptime.Monitoring.xml System Up Time Monitoring (unsealed)
Or
System.Uptime.Monitoring.mp System Up Time Monitoring (sealed)
OM2007_MP_SystemUpTime.doc This management pack guide.

How to Import the System Up Time Monitoring Management Pack
For instructions about importing a management pack, see How to Import a Management Pack in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkID=98348).
Note
Import the Windows Core Library before importing the System Up Time Monitoring Management Pack (System.Uptime.Monitoring.xml or System.Uptime.Monitoring.xml ).
Create a New Management Pack for Customizations
Below is Microsoft’s stated Best Practice:
Most vendor management packs are sealed so that you cannot change any of the original settings in the management pack file. However, you can create customizations, such as overrides or new monitoring objects, and save them to a different management pack. By default, Operations Manager 2007 saves all customizations to the default management pack. As a best practice, you should instead create a separate management pack for each sealed management pack you want to customize.
Creating a new management pack for storing overrides has the following advantages:

  • It simplifies the process of exporting customizations that were created in your test and pre-production environments to your production environment. For example, instead of exporting a default management pack that contains customizations from multiple management packs, you can export just the management pack that contains customizations of a single management pack.
  • It allows you to delete the original management pack without first needing to delete the default management pack. A management pack that contains customizations is dependent on the original management pack. This dependency requires you to delete the management pack with customizations before you can delete the original management pack. If all of your customizations are saved to the default management pack, you must delete the default management pack before you can delete an original management pack.
  • It is easier to track and update customizations to individual management packs.

For more information about sealed and unsealed management packs, see Management Pack Formats (http://go.microsoft.com/fwlink/?LinkId=108355). For more information about management pack customizations and the default management pack, see About Management Packs in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=108356).

Security Considerations

You may need to customize your management pack. Certain accounts cannot be run in an environment with minimal privileges or the account must have minimum permissions. Note: If you have imported the Microsoft Active Directory Management Pack, then the System Up Time performance counter is already being collected from Domain Controllers.

Computer Groups

You can use the following built in computer groups for leveraging the monitoring and reporting within this management pack. Or you can create your own groups (e.g. – Production IIS Servers). Groups must contain objects that are based on the Windows Computer class.
Computers Rebooted Groups

Group Contents
Computers Rebooted Daily This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled daily reboots. (86400 seconds or 1 day)
Computers Rebooted Weekly This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled weekly reboots. (604800 seconds or 7 days)
Computers Rebooted Monthly This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled Monthly reboots. (2592000 seconds or 30 days)
Computers Rebooted Quarterly This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled Quarterly reboots. (7776000 seconds or 90 days)

Understanding Management Pack Operations

This section provides information about the types of objects the System Up Time Monitoring Management Pack for Operations Manager 2007 discovers, information about classes, how health rolls up, and monitoring scenarios.

Object Discovery

The System Up Time Monitoring Management Pack requires no discovery. However, the System Up Time Monitoring Management Pack depends on the Windows Computer Base class.

Key Monitoring Scenarios

The following table provides a summary of the monitors to be created for System Up Time and under which group they are configured.
Windows Computer Monitors

Name Enabled Type Description
System Uptime Daily Reboot Monitor False Performance This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 Day (86400 seconds) and is targeted towards computers in the ‘Computers Rebooted Daily’ group.
System Uptime Weekly Reboot Monitor False Performance This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 7 Days (604800 seconds) and is targeted towards computers in the ‘Computers Rebooted Weekly’ group.
System Uptime Monthly Reboot Monitor False Performance This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 month (30 Days or 2592000 seconds) and is targeted towards computers in the ‘Computers Rebooted Monthly’ group.
System Uptime Quarterly Reboot Monitor False Performance This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 Quarter (90 days or 7776000 seconds) and is targeted towards computers in the ‘Computers Rebooted Quarterly’ group.

Windows Computer Rules

Name Enabled Type Description
System Uptime Collection Rule True Performance This rule collects the ‘System Up Time’ performance counter. By default it is configured to collect hourly.

Placing Monitored Objects in Maintenance Mode

Note: The System Up Time Monitoring and Reports may be affected when the System Uptime Collection Rule is unloaded. It may take up to an hour for the system up time value to be reflected correctly after the workflow is restarted.

When a monitored object, such as a computer or distributed application, goes offline for maintenance, Operations Manager 2007 detects that no agent heartbeat is being received and, as a result, might generate numerous alerts and notifications. To prevent alerts and notifications, place the monitored object into maintenance mode. In maintenance mode, alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts are suppressed at the agent.
For instructions about placing a monitored object in maintenance mode, see How to Put a Monitored Object into Maintenance Mode in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=108358).

Appendix: Reports

The following table summarizes the reports that are included in the System Up Time Monitoring Management Pack.
Reports

Name Description
System Up Time Report
A general system up time report, chosen by computer group, containing computer name and system up time in descending order by longest up time. Best viewed as an excel spreadsheet.

 

Name

Description
System Up Time Compliance Report
Chosen by computer group like ‘All Windows Computers’, this report shows computers that have a system up time greater than desired. Best viewed as an excel spreadsheet.

Appendix: Views

The following table lists the views that should be created for the management pack.


 

Name

Type Description
System Up Time Alerts Alert
All alerts generated from the System Up Time Monitoring Management Pack

.


 

Name

Type Description
System Up Time Performance Performance
All System Up Time performance counters on all Windows Computers
Just a standard performance view.

14 thoughts on “System Up Time Monitoring

  1. Ravi

    Hi,

    This Mp is good and i did the same thing (with VBscript using WMI Calls) for one of my customers.

    Do we have any approach where we could generate a report based on the period (date & time range) selected by the user to report the system-up time?

    regards,

    Ravi

  2. didierr

    Hi,

    I tried this MP but the reports didn’t work –> always empty. (SCOM 2007 R2 with CU2.

    Could you help me?

    Regards

  3. Rainer

    Hi

    same issue as didierr described.

    I did the following:

    1) Disabled the four group population discoveries "Populate Computers Rebooted *" because we don’t use scheduled reboots.

    2) Database collation problem: added "COLLATE database_default" to the create table statements as described here: http://social.msdn.microsoft.com/Forums/de-DE/sqlserverde/thread/2676f012-581f-4c8e-b748-d92f59532554

    The System Uptime Report runs successfully but does not deliver any data. Performance view in monitoring section works so data collection is ok.

    I’m using R2 CU3.

    Any ideas would be highly appreciated.

    Regards

    Rainer

  4. Rainer

    Hi,

    the report works now in my environment. What I did:

    In the SSRS configuration I set three default values for "StartTime", "EndTime" and "GMTOffset".

    Regards

    Rainer

  5. David Summers

    Can someone provide a clear resolution on the Collation issue with the Reports please. As I really need to get this working on our R2 SCOM 2007 hosts

  6. David Summers

    An error occurred during client rendering.

    An error has occurred during report processing.

    Query execution failed for dataset ‘DailyDataSet’.

    Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

    That is the error when trying to view the report

  7. jamesbond19731974

    Hi All,

    After importing the System Uptime MP i am getting error "Query execution failed for data set ‘dataset1’" while running the System Uptime Report.

    Please let me know how to rectify this error. Urgently Require help to rectify this issue.

  8. joedali

    I know its not a true fix but I fixed the "Query execution failed for data set ‘dataset1’" error by making my data reader account a dbo on my DW.

    Yeah, I know….

    🙂

  9. daniel@mch.com

    The Monitors and rules work great. But the reports just fail with the following error

    An error has occurred during report processing. (rsProcessingAborted)
    Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
    Arithmetic overflow error for type int, value = 8008183808.000000.

  10. Frank Lesniak

    For those with the "Query execution failed for data set ‘dataset1’" error, don’t make your data reader account a dbo. Instead, follow these steps:

    Open SQL Management Studio
    Expand OperationsManagerDW -> Programmability -> Stored Procedures -> dbo.SystemUpTimeInfoGet
    Right-click on dbo.SystemUpTimeInfoGet, then click Properties.
    Click on "Permissions"
    Click on "Search"
    Enter the name of the service account serving as the "Data Reader" (e.g. "SCOMDataReaderAcct")
    Click "Check Names"
    If prompted, check the checkbox for the appropriate user account. Click "OK"
    Click "OK" on the "Select Users or Roles" dialog.
    Under "Grant", check the checkbox for "Execute"
    Click "OK".

    On the left, right-click on dbo.SystemUpTimeComplianceDailyInfoGet, then click Properties.
    Click on "Permissions"
    Click on "Search"
    Enter the name of the service account serving as the "Data Reader" (e.g. "SCOMDataReaderAcct")
    Click "Check Names"
    If prompted, check the checkbox for the appropriate user account. Click "OK"
    Click "OK" on the "Select Users or Roles" dialog.
    Under "Grant", check the checkbox for "Execute"
    Click "OK".

    On the left, right-click on dbo.SystemUpTimeComplianceWeeklyInfoGet, then click Properties.
    Click on "Permissions"
    Click on "Search"
    Enter the name of the service account serving as the "Data Reader" (e.g. "SCOMDataReaderAcct")
    Click "Check Names"
    If prompted, check the checkbox for the appropriate user account. Click "OK"
    Click "OK" on the "Select Users or Roles" dialog.
    Under "Grant", check the checkbox for "Execute"
    Click "OK".

    On the left, right-click on dbo.SystemUpTimeComplianceMonthlyInfoGet, then click Properties.
    Click on "Permissions"
    Click on "Search"
    Enter the name of the service account serving as the "Data Reader" (e.g. "SCOMDataReaderAcct")
    Click "Check Names"
    If prompted, check the checkbox for the appropriate user account. Click "OK"
    Click "OK" on the "Select Users or Roles" dialog.
    Under "Grant", check the checkbox for "Execute"
    Click "OK".

    On the left, right-click on dbo.SystemUpTimeComplianceMonthlyInfoGet, then click Properties.
    Click on "Permissions"
    Click on "Search"
    Enter the name of the service account serving as the "Data Reader" (e.g. "SCOMDataReaderAcct")
    Click "Check Names"
    If prompted, check the checkbox for the appropriate user account. Click "OK"
    Click "OK" on the "Select Users or Roles" dialog.
    Under "Grant", check the checkbox for "Execute"
    Click "OK".

    On the left, right-click on dbo.SystemUpTimeComplianceQuarterlyInfoGet, then click Properties.
    Click on "Permissions"
    Click on "Search"
    Enter the name of the service account serving as the "Data Reader" (e.g. "SCOMDataReaderAcct")
    Click "Check Names"
    If prompted, check the checkbox for the appropriate user account. Click "OK"
    Click "OK" on the "Select Users or Roles" dialog.
    Under "Grant", check the checkbox for "Execute"
    Click "OK".

    Close SQL Management Studio.

  11. MasemolaTMB

    Hi All,

    Has any one fixed the issue where the reports are Blank?

    I have the same issue and it seems no one has given the direct answer to this problem.

    Can you please assist.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.