cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Abhi.Bajaj
AppDynamics Team

AppDynamics Machine Agent by default monitors 20 process classes. These process classes are made up of multiple of the same extension of processes and can change depending on which process is referred to as top during the time frame selected by the machine agent. The ideal way to use process monitoring using a Machine Agent can be achieved by filtering out the processes.

How to filter out the process

  • You will need to modify your ServerMonitoring.yaml file present at <MA-Home>/extensions/ServerMonitoring/conf/ServerMonitoring.yaml file
    processMonitorConfig:
      maxClassIdLength                 : 50
      processSelectorRegex             : ".*java|.*machineagent.jar|.*amazon.*|.*dockerd.*|.*containerd.*"
      minLiveTimeMillisBeforeMonitoring: 60000
      maxNumberMonitoredClasses        : 20
      processClassSelectorRegexList :
           machineAgentTasks: '.*java.*machineagent.jar'
           containerd: '.*containerd.*'
           amazon:  '.*amazon.*'
           docker: '.*dockerd.*'​

In the above example:
processSelectorRegex is used to select which processes will be monitored by the machine agent and afterward, we are grouping it by using processClassSelectorRegexList. 

A screenshot is attached to give you an idea of how it will look.
Screen_Shot_2022-04-06_at_11.49.52_AM__6_.png

Note: Same extension class example: All Java classes will be grouped together. Machine Agent is a Java process, so I grouped them in processClassSelectorRegexList.

Thanks
Abhimanyu

Version history
Last update:
‎06-10-2024 08:26 AM
Updated by:
On-Demand Webinar
Discover new Splunk integrations and AI innovations for Cisco AppDynamics.


Register Now!

Observe and Explore
Dive into our Community Blog for the Latest Insights and Updates!


Read the blog here