This eXtension works only with the standalone JAVA machine agent.
# By default the port is 80/443 ( http/https ) for the host. If there is a specific port that is being used then append it to the host # Case 1, default port : default-value="hostname" # Case 2, specific port : default-value="hostname:1234" servers: # displayName is optional if you are configuring only 1 server. If you are configuring multiple servers, configuring displayName is mandatory. # When configured displayName is added to the metric path - displayName: "" host: "" #Escape special characters using "\" username: "" #Provide password or encryptedPassword and encryptionKey. See the documentation to find about password encryption. password: encryptedPassword: "" encryptionKey: "" #Provide information about hosts and vms to monitor. # "host" will take host name you want to monitor or "*" to monitor all hosts # "vms" will take vm names in the host specified or "*" to monitor all vms in that host # "*" will fetch all the available hosts/vms. hostConfig: - host: "host1" vms: ["vm1","vm2"] - host: "host2" vms: ["*"] #Replaces characters in metric name with the specified characters. By default extension takes care of replacing "|",":",",". #Specify any other char you want to replace here. # "replace" takes any regular expression # "replaceWith" takes the string to replace the matched characters #metricPathReplacements: # - replace: "," # replaceWith: " " #Configure this based on the number of hosts and vms you want to monitor. You will get "Queue Capacity reached!! Rejecting runnable tasks.. " error if the numberOfThreads is far less than the # hosts and vms from which the extension has to collect metrics. You will have to increase numberOfThreads in this case. numberOfThreads: 15 taskSchedule: numberOfThreads: 1 taskDelaySeconds: 60 #This will create this metric in all the tiers, under this path. Please make sure to have a trailing | #metricPrefix: "Custom Metrics|vmware|Status|" #This will create it in specific Tier aka Component. Replace
. Please make sure to have a trailing |. #To find out the COMPONENT_ID, please see the screen shot here https://docs.appdynamics.com/display/PRO42/Build+a+Monitoring+Extension+Using+Java metricPrefix: "Server|Component: |Custom Metrics|vmware|Status|" # If any of the following fields are not set, the values of the specific fields are set from the system properties of the corresponding fields as specified in the comments. # If the system properties are not set for the field, then the data is retrieved from machine agent configFile. Please refer to ControllerInfoFactory for more details. # Values provided here can be overridden if the same field is configured in either controller-info.xml or system properties. controllerInfo: controllerHost: "" # -Dappdynamics.controller.hostName controllerPort: # -Dappdynamics.controller.port controllerSslEnabled: false # -Dappdynamics.controller.ssl.enabled enableOrchestration: false # N/A uniqueHostId: "" # -Dappdynamics.agent.uniqueHostId username: "admin" # -Dappdynamics.agent.monitors.controller.username password: "" # -Dappdynamics.agent.monitors.controller.password encryptedPassword: "j+0oxTzUtw2xAdaq4UUq/Q==" # -Dappdynamics.agent.monitors.controller.encryptedPassword accountAccessKey: "" # -Dappdynamics.agent.accountAccessKey account: "" # -Dappdynamics.agent.accountName machinePath: "" # -Dappdynamics.machine.agent.hierarchyPath simEnabled: false # -Dappdynamics.sim.enabled applicationName: "" # -Dappdynamics.agent.applicationName tierName: "" # -Dappdynamics.agent.tierName nodeName: "" # -Dappdynamics.agent.nodeName #Encryption key for your controllerInfo password encryptionKey: "abcd"
|Ballooned Memory||The size of the balloon driver in the VM, in MB. The host will inflate the balloon driver to reclaim physical memory from the VM. This is a sign that there is memory pressure on the host.|
|Compressed Memory||The amount of compressed memory currently consumed by VM, in Kb.|
|Overhead Memory Consumed||The amount of consumed overhead memory, in MB, for this VM.|
|Distributed CPU Entitlement||This is the amount of CPU resource, in MHz, that this VM is entitled to, as calculated by DRS. Valid only for a VM managed by DRS.|
|Distributed Memory Entitlement||This is the amount of memory, in MB, that this VM is entitled to, as calculated by DRS. Valid only for a VM managed by DRS.|
|Guest Memory Usage||Guest memory utilization statistics, in MB. This is also known as active guest memory. The number can be between 0 and the configured memory size of the virtual machine. Valid while the virtual machine is running.|
|Host Memory Usage||Host memory utilization statistics, in MB. This is also known as consumed host memory. This is between 0 and the configured resource limit. Valid while the virtual machine is running. This includes the overhead memory of the VM.|
|Overall CPU Usage||Basic CPU Usage statistics, in MHz. Valid while the virtual machine is running.|
|Overall CPU Demand||Basic CPU Demand statistics, in MHz. Valid while the virtual machine is running.|
|Private Memory||The portion of memory, in MB, that is granted to this VM from non-shared host memory.|
|Shared Memory||The portion of memory, in MB, that is granted to this VM from host memory that is shared between VMs.|
|Static CPU Entitlement||The static CPU resource entitlement for a virtual machine. This value is calculated based on this virtual machine's resource reservations, shares and limit, and doesn't take into account current usage. This is the worst case CPU allocation for this virtual machine, that is, the amount of CPU resource this virtual machine would receive if all virtual machines running in the cluster went to maximum consumption. Units are MHz.|
|Static Memory Entitlement||The static memory resource entitlement for a virtual machine. This value is calculated based on this virtual machine's resource reservations, shares and limit, and doesn't take into account current usage. This is the worst case memory allocation for this virtual machine, that is, the amount of memory this virtual machine would receive if all virtual machines running in the cluster went to maximum consumption. Units are MB.|
|Swapped Memory||The portion of memory, in MB, that is granted to this VM from the host's swap space. This is a sign that there is memory pressure on the host.|
|Uptime||The system uptime of the VM in seconds.|
|Memory MB||Memory in MB|
|Num CPU||Number of CPU Cores|
|Distributed CPU Fairness||The fairness of distributed CPU resource allocation on the host|
|Distributed Memory Fairness||The fairness of distributed memory resource allocation on the host|
|Overall CPU Usage||Aggregated CPU usage across all cores on the host in MHz. This is only available if the host is connected|
|Overall Memory Usage||Physical memory usage on the host in MB. This is only available if the host is connected|
|Up Time||The system uptime of the host in seconds.|
|Memory Size||Memory size of the host machine|
|CPU Cores||CPU core sof this host machine|
Please look at the troubleshooting document and make sure that everything is followed correctly.
For any questions or feature requests, please contact the AppDynamics Center of Excellence.
|05 May 2020|
2.1: Made compatible with JDK 1.5.
2.2 : Fixed decimal metrics issue.
2.3: Added Host metrics
2.4: Added additional metrics to Host and Vms. Displaying VM's order by Host
2.5.1: Replaced vijava with yavijava and bug fixes
2.5.2: Using latest commons to execute task and cache metrics
2.5.3: Added Licensing Files
3.0.0: Revamping and moving the extension to commons 2.2.3 which fixes log4j issues