On this Page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
18 rates
You can selectively control the number of metrics reported by individual Standalone Machine agents (including Server Visibility agents). Rather than have all agents report all the metrics all the time, you can configure individual agents to collect

  • Key Performance Indicator metrics only (KPI mode)
  • KPI and Diagnostic metrics (Diagnostic mode)
  • All available metrics (Advanced Diagnostic mode)

This provides the flexibility to report KPI metrics only on most machines and then increase the metric level on specific servers where you need deeper visibility to diagnose problems. You can increase scalability on the Controller and conserve metric bandwidth on the network with no sacrifice in visibility.

Every Basic and Server Visibility metric has a default DMM class (KPI, Diagnostic, and Advanced Diagnostic). To see the DMM class for each metric, see Hardware Resources Metrics.

Important Notes

Note the following:

  • You can disable DMM on individual agents. When DMM is disabled on an agent, that agent will report all metrics regardless of whether DMM is enabled or disabled on the Controller. Disabling DMM on an agent is recommended only for mission-critical servers and other machines for which you are sure you want to collect all metrics. For more information, see "Enable Dynamic Monitoring Mode (DMM)" under Standalone Machine Agent Configuration Properties.
  • If you switch the monitoring mode in the Controller from a more-inclusive to a less-inclusive mode, the Metric Browser will show values for the newly-excluded metrics for one hour after the switch. For example: suppose you switch from Diagnostic to KP mode. For any Diagnostic metric, the Metric Browser will report a steady line (at 0 or the last-reported value) for one hour after the switch; then the line will disappear. This is standard behavior in the Metric Browser for any agent when it stops reporting a specific metric.
  • Each Standalone Machine Agent has a set of configurable settings that specify the volumes, networks, and processes to report and to ignore. For example, you can define a process whitelist (report on matching processes) and blacklist (ignore matching processes). An agent will not report metrics for items excluded by its local settings, regardless of the monitoring mode. For more information, see Machine Agent Settings for Server Visibility
  • If you have any custom health rules based on Diagnostic or Advanced Diagnostic metrics, DMM might cause these rules to generate "false-positive" alerts. (Standard, non-custom health rules are not affected.) If you have any health rules like this, the workaround is to edit the rule to use a KPI metric in place of the Diagnostic or Advanced Diagnostic metric.  

Initial Setup

DMM is enabled by default. To configure DMM, do the following:

  1. Log in to the Controller administration console using the root user password. For more information, see Access the Administration Console.

    http://<controller host>:<port>/controller/admin.jsp
  2. Set the following options:
    1. sim.machines.dmm.defaultMode = KPI (Sets the default mode to KPI on all Standalone Machine Agents). 
    2. sim.machines.dmm.dmmAllowed = true (Enables Dynamic Monitoring Mode on the Controller)
  3. For servers of interest that require additional visibility, increase the monitoring mode to Diagnostic or Advanced Diagnostic. To change the monitoring mode of one or more agents, do the following:
    • Log in to the Controller UI and click Servers.
    • In the Servers table, select the servers whose monitoring mode you want to change.
    • Right-click in the selection, choose Select Dynamic Monitoring Mode, and select the new mode.

Example Workflow

After you complete the initial setup, you can set the Dynamic Monitoring Mode on individual machine agents as needed. An example workflow might look like the following:

  • The DevOps team for a large enterprise monitors its IT infrastructure using Standalone Machine Agents (1,000-plus agents monitoring servers in hundreds of locations). All agents are initially set to KPI mode. 
  • One agent reports a lot of disk read/write operations (KPI metric) on critical-server-A.
  • Set the agent DMM on critical-server-A to Diagnostic.
  • Monitor the amount of data read and written for the entire disk and for each partition (Diagnostic metrics) on critical-server-A.
  • If the Diagnostic metrics do not indicate the source of the problem, and further investigation is needed, set the agent DMM to Advanced Diagnostic.
  • Monitor average queue times and read/write times for each partition (Advanced Diagnostic metrics) on critical-server-A.
  • When advanced diagnostics are no longer required on critical-server-A, set the agent DMM back to KPI.

 


  • No labels