AppDynamics Extension for Google Compute Engine Monitoring

This extension works only with the standalone machine agent.


Use Case


With GCE we can run large-scale workloads on virtual machines hosted on Google's infrastructure. The GCE monitoring extension captures statistics from the GCE and displays them in the AppDynamics Metric Browser.




Create a service account for your GCE project and download the privatekey file (.p12 file). To do this:

1. Log into the Google Cloud Console

2. Click on the project you want to use the GCE monitoring extension with (or create one if you don't have one yet).
3. Click "APIs & auth" in the left sidebar
4. Click "Credentials" in the left sidebar
5. Click "Create New Client ID" and choose "Service Account"
A private key file (.p12 file) will be downloaded for you. Note the password for the private key! This private key is your client private key.




  1. Download and unzip the file 'target/' to <machineagent install dir>/monitors
  2. Open monitor.xml and configure the GCE arguments
<argument name="ServiceAccountId" is-required="true" default-value=""  />
<argument name="ServiceAccountP12FilePath" is-required="true" default-value="/home/.../GCE/privatekey.p12" />
<argument name="ProjectID" is-required="true" default-value="appdynamics-gce" />

ServiceAccountId : GCE Project service account id
ServiceAccountP12FilePath : GCE Project service account private key
ProjectID : GCE Project ID

3. Restart the Machine Agent


In the AppDynamics Metric Browser, look for: Application Infrastructure Performance | <Tier> | Custom Metrics | GCE




The following metrics are reported.



Metric PathDescription
GCE/{Project ID}/Disk/{Zone}/{Disk Name}/SizeinGbSize of the Disk in Gb



Metric PathDescription
GCE/{Project ID}/Quota/FIREWALLS/LimitNumber of fire walls allowed
GCE/{Project ID}/Quota/FIREWALLS/UsageNumber of fire walls used
GCE/{Project ID}/Quota/FORWARDING_RULES/LimitNumber of forwarding rules allowed
GCE/{Project ID}/Quota/FORWARDING_RULES/UsageNumber of forwarding rules used
GCE/{Project ID}/Quota/HEALTH_CHECKS/LimitNumber of health checks allowed
GCE/{Project ID}/Quota/HEALTH_CHECKS/UsageNumber of health checks used
GCE/{Project ID}/Quota/IMAGES/LimitNumber of images allowed
GCE/{Project ID}/Quota/IMAGES/UsageNumber of images used
GCE/{Project ID}/Quota/NETWORKS/LimitNumber of networks allowed
GCE/{Project ID}/Quota/NETWORKS/UsageNumber of networks used
GCE/{Project ID}/Quota/ROUTES/LimitNumber of routes allowed
GCE/{Project ID}/Quota/ROUTES/UsageNumber of routes used
GCE/{Project ID}/Quota/SNAPSHOTS/LimitNumber of snapshots allowed
GCE/{Project ID}/Quota/SNAPSHOTS/UsageNumber of snapshots used
GCE/{Project ID}/Quota/TARGET_INSTANCES/LimitNumber of target instances allowed
GCE/{Project ID}/Quota/TARGET_INSTANCES/UsageNumber of target instances used
GCE/{Project ID}/Quota/TARGET_POOLS/LimitNumber of target pools allowed
GCE/{Project ID}/Quota/TARGET_POOLS/UsageNumber of target pools used



Metric PathDescription
GCE/{Project ID}/Region/{region}/Quota/CPUS/LimitNumber of CPUs allowed
GCE/{Project ID}/Region/{region}/Quota/CPUS/UsageNumber of CPUs used
GCE/{Project ID}/Region/{region}/Quota/DISKS_TOTAL_GB/LimitDisk size allowed
GCE/{Project ID}/Region/{region}/Quota/DISKS_TOTAL_GB/UsageDisk size used
GCE/{Project ID}/Region/{region}/Quota/IN_USE_ADDRESSES/Limitin-use addresses allowed
GCE/{Project ID}/Region/{region}/Quota/IN_USE_ADDRESSES/Usagein-use addresses used
GCE/{Project ID}/Region/{region}/Quota/STATIC_ADDRESSES/Limitstatis addresses allowed
GCE/{Project ID}/Region/{region}/Quota/STATIC_ADDRESSES/Usagestatis addresses used


Custom Dashboard

Screen Shot 2014-03-02 at 12.44.57 PM.png 




Always feel free to fork and contribute any changes directly via GitHub.




For any support questions, please contact






Last Update: