The administrators can now apply Agent G2 process monitoring templates including the existing G1 templates for Linux and Windows devices. The Agent G2 templates allow threshold and filter configuration at the component-level.

Agent G2 process statistics monitors

The following global templates are used to monitor devices.

Template NameSupported Metrics
Agent G2 - Linux Process Monitoringsystem.process.stats.count system.process.stats.cpu system.process.stats.memory system.process.stats.threads system.process.stats.open.fds
Agent G2 - Windows Process MonitoringSystem.windows.process.count System.windows.process.handlecount System.windows.process.pagefilebytes System.windows.process.processorcoretime.percent System.windows.process.processortime.percent System.windows.process.threadcount System.windows.process.workingset
  1. Select a client from the All Clients list.

  2. Go to Infrastructure > Resources.

  3. From Resources, click the Resource Name > Resource Details > Monitors > Template.

  4. From the Templates screen, click +Assign Templates.

  5. From Apply Templates > Select Templates > Available templates, select the templates. The Selected templates section displays the selected templates.

  6. Click Assign.

  7. From the Enter Configurations section, enter a Value for the configuration parameters.

    Apply Template
  8. Click Submit. The Templates screen displays the selected templates.

After applying the template to a device, validate the template to ensure that it is assigned to a resource.

Configuration parameters

Use the following input argument format for Linux and Windows process patterns: processname@@@processname@@@processname. This format provides a delimiter (@@@) separation for the regex patterns while monitoring multiple processes. The processname entered in the format is the name of the process that you want to monitor, for example, a regular expression string.

The Agent supports every basic and extended regular expressions such as:

  • grep with -E switch-based regular expressions for Linux.
  • PowerShell-based regular expressions for Windows.

Examples:

  • opsramp-agent@@@opsramp-shield: The component name is the respective process name.
  • opsramp-.*@@@chrome: The component name is the respective process name and other process names matching with a given regular expression.
  • (ntpd|chrond)@@@notepad.*: The component name is the process name matching with a given regular expression. If the string notepad.* matches with two process names such as notepad.exe and notepad++.exe. The component names are Notepad and Notepad++.
  • Use respective display names for each component while monitoring the same process with different arguments. For example, processPattern1;;;DisplayName1@@@processPattern2;;;DisplayName2. The component names are the display names for the respective process patterns.
  • enter the same display name while configuring component filter or component thresholds at the template or device level. For example, svchost.*NetworkService;;;svchost_NetworkService@@@svchost.*DcomLaunch;;;svchost_DcomLaunch. Use the component name svchost_NetworkService and svchost_DcomLaunch while defining the component filters and component thresholds.

Collect data

The collected metrics can be viewed with the following name in Infrastructure > Resources > Device Details > Monitors > Monitors.

  • Windows: Agent G2 - Windows Process Monitoring
  • Linux: Agent G2 - Linux Process Monitoring

Validate templates

The graphical data is displayed for each metric name configured in the process statistics monitor. The graphs can be viewed under Infrastructure > Resources > Device Details > Metrics. Use the metric drop-down menu to view the graph for each metric.

Validate Template

Process statistics alert

All alerts are sent while monitoring processes and can be viewed in the Alert browser. Examine the alert subject to verify process alert details.

Process Alerts