Microsoft System Center Operations Manager 2012 (Management Server)

Version 1

    This template assesses the status and overall health of services as well as the performance of the Microsoft System Center Operations Manager 2012 Management Server.


    Prerequisites: WMI access to the target server.

    Credentials: Windows Administrator on the target server.


    Note: You need to set thresholds for these counters according to your environment. It is recommended to monitor these counters for some period of time to understand potential value ranges and then set the thresholds accordingly. For more information, see http://knowledgebase.solarwinds.com/kb/questions/2415.

    Service: System Center Data Access


    Monitored Components

    Service: System Center Data Access

    This monitor returns the memory and CPU usage of the Microsoft System Center Data Access Service.

     

    Service: System Center Management Configuration

    This monitor returns the memory and CPU usage of the Microsoft System Center Management Configuration service.

     

    Service: Operations Manager Audit Collection

    This monitor returns the memory and CPU usage of the Operations Manager Audit Collection service. This service is used for receiving audit events over the network and writing them to a database.

     

    DB Write Action Caches: Cache Hit Ratio

    This monitor returns the hit ratio for the cache.

    Note: By default, this counter monitors the managedentityidcache instance. You may change it if you need. Look in the Windows perfmon utility to see all the available instances for this counter.

     

    DB Write Action Caches: Cache Size

    This monitor returns the number of entries in the cache.

    Note: By default, this counter monitors the managedentityidcache instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DB Write Action Modules: Avg. Batch Size

    This monitor returns the number of entries processed by the module, on average.

    Note: By default, this counter monitors the performancewritemodule instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DB Write Action Modules: Avg. Processing Time

    This monitor returns the amount of time it takes to process an incoming batch, on average.

    Note: By default, this counter monitors the performancewritemodule instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Synchronization Module: Avg Batch Processing Time, ms

    This monitor returns the amount of time it takes to process an incoming batch, on average, in ms.

    Note: By default, this counter monitors the managedentity instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Synchronization Module: Avg. Batch Size

    This monitor returns the number of entries processed by the module, on average.

    Note: By default, this counter monitors the managedentity instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Synchronization Module: Batches/sec

    This monitor returns the number of batches per second.

    Note: By default, this counter monitors the managedentity instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Synchronization Module: Data Items/sec

    This monitor returns the number of data items, per second.

    Note: By default, this counter monitors the managedentity instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Synchronization Module: Errors/sec

    This monitor returns the number of errors, per second.

    Note: By default, this counter monitors the managedentity instance. You may change it if you need. Look in Windows the perfmon utility to see all available instances for this counter.

     

    DW Writer Module: Avg Batch Processing Time, ms

    This monitor returns the amount of time it takes to process an incoming batch, on average, in ms.

    Note: By default, this counter monitors the performance instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Writer Module: Avg. Batch Size

    This monitor returns the number of entries processed by the module, on average.

    Note: By default, this counter monitors the performance instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Writer Module: Batches/sec

    This monitor returns the number of batches, per second.

    Note: By default, this counter monitors the performance instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Writer Module: Data Items/sec

    This monitor returns the number of data items, per second.

    Note: By default, this counter monitors the performance instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    DW Writer Module: Errors/sec

    This monitor returns the number of errors, per second.

    Note: By default, this counter monitors the performance instance. You may change it if you need. Look in the Windows perfmon utility to see all available instances for this counter.

     

    OpsMgr Connector: Bytes Received

    This monitor returns the total number of network bytes which have been received by the MOM connector, per second.  This may be more or less than the number of data bytes received due to compression and encryption.

     

    OpsMgr Connector: Bytes Transmitted

    This monitor returns the total number of network bytes which have been transmitted by the MOM connector, per second.  This may be more or less than the number of data bytes submitted for transmission due to compression and encryption.

     

    OpsMgr Connector: I/O Errors

    This monitor returns the number of I/O errors encountered by the connector, per second.

     

    OpsMgr Connector: I/O Operations Timed Out
    This monitor returns the number of I/O operations that have timed out.

     

    OpsMgr Connector: Open Connections

    This monitor returns the number of TCP/IP connections currently open in the connector.

     

    OpsMgr Connector: Server Listen Queue Length

    This monitor returns the number of outstanding listen requests which are queued.  If this drops to zero, the connector will not be able to accept incoming connections.

     

    OpsMgr Connector: Fragmented Compression Packets

    This monitor returns the number of compression packets which were received by the connector and had to be reassembled, per second.  This can be caused by a number of factors, including the size of the packet, the MTU of the network interface, quantity of traffic on the network, and/or the amount of load on the connector. Packet re-assembly can hurt performance and the ability of the server to scale.

     

    OpsMgr Connector: Fragmented Data Packets

    This monitor returns the number of data packets which were received by the connector and had to be reassembled, per second.  This can be caused by a number of factors, including the size of the packet, the MTU of the network interface, quantity of traffic on the network, and/or the amount of load on the connector.  Packet re-assembly can hurt performance and the ability of the server to scale.

     

    OpsMgr Connector: Fragmented Encryption Packets

    This monitor returns the number of encrypted packets which were received by the connector and had to be reassembled, per second. This can be caused by a number of factors, including the size of the packet, the MTU of the network interface, quantity of traffic on the network, the encryption algorithm used and/or the amount of load on the connector.  Packet re-assembly can hurt performance and the ability of the server to scale.

     

    OpsMgr Connector: Fragmented Session Packets

    This monitor returns the number of session packets which were received by the connector and had to be reassembled, per second.  This can be caused by a number of factors, including the size of the packet, the MTU of the network interface, quantity of traffic on the network, and/or the amount of load on the connector.  Packet re-assembly can hurt performance and the ability of the server to scale.


    OpsMgr Connector: Fragmented SSPI Packets

    This monitor returns the number of SSPI negotiation packets which were received by the connector and had to be reassembled, per second.  This can be caused by a number of factors, including the size of the packet, the MTU of the network interface, quantity of traffic on the network, and/or the amount of load on the connector.  Packet re-assembly can hurt performance and the ability of the server to scale.

     

    Events: OpsMgr Management Configuration Events

    This monitor returns the number of warning and error events with the following source name: OpsMgr Management Configuration. For any and all events, you should investigate the “Operations Manager” Event Log.

     

    Events: OpsMgr Connector and Network Discovery Events

    This monitor returns the number of warning and error events with the following source names: OpsMgr Connector, OpsMgr Network Discovery, OpsMgr Root Connector. For any and all events, you should investigate the “Operations Manager” Event Log.

     

    Events: OpsMgr Config Service Events

    This monitor returns the number of warning and error events with the following source name: OpsMgr Config Service. For any and all events, you should investigate the “Operations Manager” Event Log.

     

    Events: OpsMgr SDK Service Events

    This monitor returns the number of warning and error events with the following source name: OpsMgr SDK Service. For any and all events, you should investigate the “Operations Manager” Event Log.

     

    TCP Port: SCOM (5723)

    This component monitor tests the ability of a SCOM to accept incoming sessions. By default, this component monitors TCP port 5723.

     

    TCP Port: SCOM (5724)

    This component monitor tests the ability of a SCOM to accept incoming sessions. By default, this component monitors TCP port 5724.

     

    This documentation is based on “System Center 2012 Operations Manger Unleashed” book.