The following procedure is an example of how you create an alert logging latency report for a managed computer. An alert logging latency report shows you how much time it took from when an alert was generated until it was written into the Operations Manager database. An alert is not displayed in the Operations console until after it is written into the Operations Manager database. Alert latency can be a function of network delays in your environment.

This information is useful when considering service level agreements (SLA). You might not want to commit to an SLA of 2 minutes if alerts take longer than that to get written into the Operations Manager database.

Note
Operations Manager 2007 Reporting must be installed before you can run an alert logging latency report.

To create an alert logging latency report

  1. Log on to the computer with an account that is a member of the Operations Manager Administrators role for the Operations Manager 2007 management group.

  2. In the Operations console, click the Monitoring button.

  3. In the Monitoring pane, expand Monitoring and then click Computers.

  4. In the Computers pane, click a row with a Health Service instance.

  5. In the Actions pane, under Windows Computer Reports, click Alert Logging Latency.

  6. In the Parameter Area, click the down arrow in the From box and then click Yesterday.

    Note
    You can further specify the timeframe for the report in the additional options in the Parameter Area.

  7. Click the down arrow on the Threshold list, and select the latency threshold you want to measure.

  8. Click the down arrow on the Aggregation Type list, and click the value you want for this report.

  9. Click Run to display the Alert Logging Latency Report.

  10. Click Close to close the report.

See Also

Did you find this information useful? Please send your suggestions and comments about the documentation.