Discussion Feed

Hi Walter, There are a number of metrics available for every process, and depending on how you've configured the "Monitoring Mode", you'll see more as you enable "KPI", "Advanced", or "Diagnostic" detail.  If you enable "Advanced" via configuration or interactively via the UI, you will see the process "Count" metric collected. e.g. Application Infrastructure Performance|Root|Individual Nodes|cvpcclab|Hardware Resources|Process|tomcat9|Count Your Health Rule should trigger when Count < 1, and "Evaluate true on no data" if you want to be alerted when the agent stops reporting to the Controller for any reason. You will specify a Custom Metric Path for the metric, e.g. Hardware Resources|Process|tomcat9|Count ... View more

Since the API does not provide a "filter by Health Rule Name" option, your best bet is to fetch all the Health Rule violations, then iterate through them and ignore the ones not associated with the target Health Rule.   Regards, ... View more

The AppDynamics Controller manages a pool of licenses. When a new JVM is started with the -javaagent and -D agent terms, the agent will connect to the Controller and request a license. If a license is available, the JVM will come up instrumented and continue to report to the Controller until the JVM is shut down. The license will be released back into the pool within five minutes of the JVM shutdown. If a license is not available, the JVM will startup instrumented, but the agent will not collect or publish any data, but will continue to ping the Controller every minute to determine if a license is available. If a license becomes available, the agent will turn itself back on and start reporting metrics to the Controller.   License Management Scope configuration allows you to assign licenses to specific applications and machines. Using scopes to configure licenses allows you to express and scale the configuration modules as required. https://docs.appdynamics.com/display/PRO45/License+Management has details.     Another customer set up a Web Service that's called from the app server startup script with App Name, Tier Name, Node Name. The Web Service determines if the target JVM should be instrumented based on a local lookup, If the JVM should be instrumented, the Web Service will return the agent terms, -javaagent and -D's, and the JVM will start up instrumented. If the JVM doesn't match the criteria for instrumentation, the Web Service returns nothing and the JVM starts up without instrumentation.   Hope these two possible approaches help you, ... View more

According to https://docs.appdynamics.com/display/PRO45/Hardware+Resources+Metrics: Avg IO Utilization (%): The average time spent processing read/write requests on all disks and partitions as a percentage of the total reported time window. Databases often report high disk I/O utilization due to frequent read/write requests. For example, if the agent detects read/write processing in 55 out of 60 seconds, the Avg IO Utilization for that minute is 92%. This metric does not measure the amount of available disk space or read/write request sizes. Regards, ... View more