Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I want to Monitor my Chrome Process count and Memory utilized by individuals chrome process.
metricPrefix: "Server|Component:Test1|Custom Metrics|Process Monitor|"
# metricPrefix: "Custom Metrics|Process Monitor|"
# displayName: required - Metrics to be reported under this name in Controller's Metric Browser
# regex/pid/pidFile - process is fetched using this field
- displayName: "machine agent"
regex: ".*java.exe -jar machineagent.jar"
- displayName: "Chrome Monitoring"
regex: ".* chrome.exe"
# Not necessary to modify
process: "ps -eo pid,%cpu=CPU%,%mem=Memory%,rsz=RSS,args"
process: "ps -eo pid,pcpu=CPU%, -o pmem=Memory%, -o rss=RSS -o args"
process: "ps -eo pid,pcpu=CPU%,pmem=Memory%,rss=RSS,args"
alias: "Resident Set Size"
- Running Instances:
alias: "Running Instances"
# number of concurrent tasks
# This is to run this in scheduled mode. In this case, the extension will fetch the data every 300 seconds
# and caches the data. The cached data will be reported to controller every min. This way there is no metric drop.
# Can be used when the data rarely changes or to reduce the load while fetching metrics every minute.
# numberOfThreads: 1
# taskDelaySeconds: 300
Solved! Go to Solution.
It would be great if you were able to share any learnings from your exchange with support back on your post. This helps keep knowledge sharing alive in the community.
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.