Monitoring Managed Nodes

ArcSight Management Center monitoring, on the Dashboard > Monitoring Summary page, displays the current health history of all managed nodes, both software and hardware.

You can view a complete list of monitored parameters in Monitoring Rules Parameters , and use them in creating your own custom rules. These rules breaches will also be displayed on the Health History and Hardware Status panels. Note that the layout and selection of the data panels in the Monitoring Summary is not customizable.

Configuring Properties for Monitoring Managed Nodes

The default properties values for node monitoring are set to work on most customer environments. If ArcMC has a heavy inventory and metrics are not being shown correctly, you may wish to configure these properties with custom values.

Configuration property Description Default Type
monitoring.node.status.taskBatchSize Number of tasks to add to the thread pool at once. It will optimum to set a value equal or half of corePoolSize. 20 Number
monitoring.node.status.timeout Timeout in seconds for a batch of tasks to complete 120 Number
monitoring.node.status.corePoolSize Size of the thread pool for executing tasks.  50 Number
monitoring.node.status.maxPoolSize Max size of the thread pool. This limit overrides corePoolSize when the value is greater than maxPoolSize. The maximum value is 300. 100 Number
monitoring.node.status.trackCancelledEntities Logged cancelled entities after reaching max set attempts. false Boolean
monitoring.node.status.evaluateCancelledAttempts Increments the cancelled counter on the entity after x number of attempts. 5 Number
monitoring.node.status.cancelledPollThreshold Log when an entity reaches its cancelled poll threshold. 2 Number

To configure monitoring properties:

  1. In a text editor, open the file In a text editor, open the file .../userdata/arcmc/logger.properties. If the file does not exist, follow the steps outlined here.

  2. Change the values of one or more properties listed above as needed.

  3. Save the file.

  4. Restart the ArcMC web processes.