Skip to content

Пакет управления для мониторинга SCSM 2012 из OpsMgr 2012

Пакет управления для мониторинга SCSM 2012 из OpsMgr 2012 published on 2 комментария к записи Пакет управления для мониторинга SCSM 2012 из OpsMgr 2012

Новость не первой свежести, но как-то я упустил момент сделать заметку. 01.06.2012 вышел пакет управления для мониторинга SCSM 2012 с помощью OpsMgr 2012.

Напомню, что агент OpsMgr 2012 нельзя устанавливать на сервера управления SCSM 2012, поэтому поддерживается только безагентный мониторинг. Как всегда, читаем внимательно документацию к пакету, чтобы не удивляться, почему ничего не работает.

Поддерживаются следующие сценарии мониторинга (копи-паст из документации к пакету):

Monitoring scenario Description Associated rules and monitors
Services Running on the   Management Server Monitoring the following   services:

  • System   Center Data Access Service
  • System   Center Management Configuration service
  • System   Center Management service
  • Microsoft.ServiceManager.SDKService.ServiceMonitor
 Indicates whether the System   Center Data Access Service is running.

  • Microsoft.ServiceManager.ConfigurationService.ServiceMonitor

Indicates whether the System   Center Management Configuration service is running.

  • Microsoft.ServiceManager.HealthService.AvailabilityHealthRollup

Indicates whether the System   Center Monitoring Pack for System Center 2012 – Service Manager   service is running and whether it is available.
Workflows Running on a Service Manager   Management Server Monitoring the following   workflows:

  • Windows   Workflow Foundation (WWF) workflows
  • System   Workflows
  • Connectors
Windows Workflow Foundation   Workflows Monitoring rules check the value   in the workflow Status column. Depending on the value,   they detect the following possible workflow failures:

  • A   workflow cannot be triggered, or the associated tasks cannot be submitted.
  • A   workflow finishes running successfully, but the output has an exception.
  • A   workflow starts running but times out. This indicates that the workflow ran   for more than 25 minutes.
  • A   workflow fails while running.
 The following rules are used for   this monitoring task, and the default interval for these rules is four hours:

  • Microsoft.SystemCenter.ServiceManager.WWF.Monitoring.RuleException:

Status of 2 indicates that the   workflow ran successfully, but it has an exception in the output.

  • Microsoft.SystemCenter.ServiceManager.WWF.Monitoring.RuleRunning:

Status of 1 or 2 indicates that   the workflow has been running for more than 25 minutes, and it is likely that   the workflow timed out.

  • Microsoft.SystemCenter.ServiceManager.WWF.Monitoring.RuleFailed:

Status of 3 indicates that the   workflow failed.

  •  Microsoft.SystemCenter.ServiceManager.WWF.Monitoring.RuleTaskSubmitError:

Status of NULL indicates that   the workflow cannot submit tasks, possibly as a result of an infrastructure   error. In this case, there is no entry in the JobStatus   table, and Status is set to NULL.

A single monitor displays the   overall health of the WWF workflows. This monitor uses an Object Linking and   Embedding Database (OLEDB) probe, and it returns a count of the number of   rows with any one of the failure conditions. If the count is 0, indicating   that there are no failures, the monitor is green. If the count is not 0, the   monitor is yellow, and it generates an alert message that directs the user to   look for details in the active alerts view.
Linking Framework Workflows Monitoring rules check the value   in the connector Status column. Depending on the value,   they detect the following possible workflow failures:

  • The   connector was created, but data synchronization did not start after more than   5 minutes.
  • Data   synchronization starts and completes but with an error.
  • The   connector is in an unknown status.
 The following rules are used for   this monitoring task, and the default interval for these rules is four hours:

  • Microsoft.SystemCenter.ServiceManager.Lfx.Monitoring.NeverRun:

Status of NeverRun, combined   with a difference between timestarted and timefinished that is greater than 5   minutes, causes the generation of an alert.

  • Microsoft.SystemCenter.ServiceManager.Lfx.Monitoring.FinishedwithError:

Status of FinshedwithError   indicates that an error occurred during data synchronization.

  • Microsoft.SystemCenter.ServiceManager.Lfx.Monitoring.Unknown:

Status that is unknown causes   the generation of an alert.

A monitor checks for any of the   failures. If there is a record that indicates a NeverRun, FinishedWithError,   or Unknown status, an alert is generated.
Grooming Workflows Monitoring for the following   possible failures:

  • A   workflow fails with a status of 2.
  • A   workflow times out.
 A monitor extracts the status for   the grooming workflows from the InternalJobHistory table. When the monitor   detects a failure, it generates an alert with a generic message that   references grooming workflows. In this case, the state of the monitor is set   to red.If a workflow’s status is Started   and it has been running for more than 25 minutes, it is likely that the   workflow timed out. However, in the case of the SubscriptionGroomingLogs   workflow, the interval is set to 15 minutes because the run time for that   workflow is less than 15 minutes.
Operations Manager Connector   Workflows Monitoring for failures that are   associated with data synchronization and other failures that are detected in   event logs. A monitor that checks event logs   to detect problems and failures. The following events cause the generation of   an alert, and they change the state of the monitor to red:

  • Event   ID 34073 – Unexpected error while creating/updating incident from alert.
  • Event   ID 34076 – Underlying Linking Framework connector instance for sync workflow   is missing.
  • Event   ID 34080 – Generic error from the Service Manager SDK.
  • Event   ID 34081 – Unhandled exception during synchronization.
  • Event   ID 34090 — Scheduled synchronization cannot start.

For the monitor to turn back to a   green/healthy state, the following events must be detected:

  • Event   ID 34084 — CI synchronization.
  • Event   ID 34089 – Processed alert in Service Manager via connector.

Скачать пакет можно здесь.

Мониторинг с помощью OpsMgr 2007 R2 не поддерживается (и с вероятностю 99% никогда не будет добавлен).

Поделиться в соц. сетях

Primary Sidebar