Remote Monitoring & Management Help

Critical Events Check

This Check scans the selected Windows Event Logs on the device for any Error Events recorded during the past 24-hours. This is a good catch-all that may show growing problems on the machine, highlighting areas for investigation with the option to run this Check in Alert or Report Mode.

Alert Mode

Report Mode

Posts a red exclamation box to the Dashboard when any Error Events are detected that match the Check criteria.

Generate an Alert (where configured)

Summary information will be available by clicking 'more info' on your Dashboard

Summary information will be shown on your Critical Events Report*.

Post a green tick on the Dashboard when any Error Events are detected that match the Check criteria.

No Alert is generated (regardless of configuration)

Summary information will be available by clicking 'more info' on your Dashboard

Summary information will be shown on your Critical Events Report*.

How Our Users Put This to Work

They use Alert Mode for increased visibility of any failures as they are reported on the Dashboard and where configured via Alerts, email or SMS.

They use Report Mode to reduce noise as the Dashboard stays green with no Alerts sent. Rather they use the Critical Event Reports to identify any devices requiring attention with this report sent to the relevant technician or distribution group each morning after that day's Daily Safety Checks have completed.

For servers there is an associated Critical Events Report which shows a device-by-device summary of the Error Events on servers across the whole customer base. It can be viewed from the Dashboard or emailed each morning (See Reports then Critical Event Report on the Dashboard.)

Frequently occurring non-critical Error Events may be recorded on a daily basis and these can be added to the Critical Event Exclusion List which is a global option applied to every Client. Once added the Event will no longer generate an Alert, appear on the Dashboard or in the Critical Event Report.

Dashboard Check configuration

Add

  1. Select the device in the north pane of the Dashboard
  2. Go to the Checks tab
  3. Click Add Check
  4. Choose Add DSC > Critical Even Check
    1. Select the required Windows Critical Event from the Critical Event drop down

    2. Choose the information to be returned in the Show summary for section (10 most recent or 10 most frequent)
    3. Configure the and Report or Alert Mode behavior in If errors found.

  5. To run an Automated Task when the Check fails choose Assign a Task after creating the Check
  6. OK to save and apply
  7. Where Assign a Task after creating the Check is selected:
    1. Select the script
    2. Click Next to configure
  8. Enter the Command Line parameters (if required)
  9. Set a Script timeout in the range 1 - 3600 seconds (default 120 seconds)
  10. Click Finish to save and apply

Edit

  1. Select the device in the north pane of the Dashboard
  2. Go to the Checks tab
  3. Select the target Critical Even Check
  4. From the Check drop-down
  5. Click Edit Check (also available from the Check's right-click menu)
  6. Configure the settings
  7. Click OK to save and apply

Delete

  1. Select the device in the north pane of the Dashboard
  2. Go to the Checks tab
  3. Select the target Critical Even Check
  4. From the Check drop-down
  5. Click Delete Check (also available from the Check's right-click menu)
  6. Enter the password you have logged into the Dashboard under to confirm removal
  7. Click OK to delete

More Information

Once the Check results are uploaded to the Dashboard details of the output can be viewed in the More Information section along with links to the following resources for further information on the Event.

The Dashboard displays in excess of ten Events depending on the number of Events discovered that match the Check criteria, however the email Alert will only show the ten most frequent or ten most recent Events.

The time and date recorded for the discovered Event is based on the local time of the device and not the Dashboard timezone.