Connect to Google Cloud Platform to see all your Google Compute Engine (GCE) hosts in Datadog. You’ll see your hosts in the infrastructure overview in Datadog and be able to sort through them easily, since Datadog automatically tags them with GCE host tags and any GCP labels you’ve added.
Related integrations include:
| App Engine | platform as a service to build scalable applications |
| Big Query | enterprise data warehouse |
| CloudSQL | MySQL database service |
| Compute Engine | high performance virtual machines |
| Container Engine | kubernetes, managed by google |
| Datastore | NoSQL database |
| Firebase | mobile platform for application development |
| Functions | A serverless platform for building event-based microservices |
| Machine Learning | machine learning services |
| Pub/Sub | real-time messaging service |
| Spanner | horizontally scalable, globally consistent, relational database service |
| Stackdriver Logging | real-time log management and analysis |
| Storage | unified object storage |
| VPN | managed network functionality |
The Datadog <> Google Cloud integration uses Service Accounts to create an API connection between Google Cloud and Datadog. Below are instructions for creating the service account and providing Datadog the service account credentials to begin making API calls on your behalf.
Press Create credentials and then select Service account key
In the Service account dropdown, select New service account
Give the service account a unique name
For Role, select Compute engine —> Compute Viewer and Monitoring —> Monitoring Viewer
Note, these roles allow us to collect metrics, tags, events, and GCE labels on your behalf.
Select JSON as the key type, and press create
Take note where this file is saved, as it is needed to complete the integration
Navigate to the Datadog Google Cloud Integration tile
Select Upload Key File to integrate this project with Datadog
Optionally, you can use tags to filter out hosts from being included in this integration. Detailed instructions on this can be found below
Press Install/Update
For each project you want to monitor, repeat this process
Google Cloud billing, the Stackdriver Monitoring API and the Compute Engine API must all be enabled for the project(s) you wish to monitor.
Optionally, you can limit the GCE instances that are pulled into Datadog by entering tags in the Limit Metric Collection textbox. Only hosts that match one of the defined tags will be imported into Datadog. You can use wildcards (‘?’ for single character, ‘*’ for multi-character) to match many hosts, or ‘!’ to exclude certain hosts. This example includes all c1 sized instances, but excludes staging hosts:
datadog:monitored,env:production,!env:staging,instance-type:c1.*
|
gcp.loadbalancing.https.backend_latencies.avg (gauge) |
Average latency of request sent by the proxy to backend until proxy receives last byte of response from backend. shown as millisecond |
|
gcp.loadbalancing.https.backend_latencies.samplecount (count) |
Sample Count of latency of request sent by the proxy to backend until proxy receives last byte of response from backend. shown as millisecond |
|
gcp.loadbalancing.https.backend_latencies.sumsqdev (gauge) |
Sum of Squared Deviation for latency of request sent by the proxy to backend until proxy receives last byte of response from backend. shown as millisecond |
|
gcp.loadbalancing.https.frontend_tcp_rtt.avg (gauge) |
Average RTT for each connection between client and proxy. shown as millisecond |
|
gcp.loadbalancing.https.frontend_tcp_rtt.samplecount (count) |
Sample Count of RTT for each connection between client and proxy. shown as millisecond |
|
gcp.loadbalancing.https.frontend_tcp_rtt.sumsqdev (gauge) |
Sum of Squared Deviation of RTT for each connection between client and proxy. shown as millisecond |
|
gcp.loadbalancing.https.request_bytes_count (count) |
Bytes sent as requests from clients to L7 load balancer. shown as byte |
|
gcp.loadbalancing.https.request_count (count) |
Number of requests served by L7 load balancer. shown as request |
|
gcp.loadbalancing.https.response_bytes_count (count) |
Bytes sent as responses from L7 load balancer to clients. shown as byte |
|
gcp.loadbalancing.https.total_latencies.avg (gauge) |
Average latency calculated from request received by proxy until proxy sees ACK from client on last response byte. shown as millisecond |
|
gcp.loadbalancing.https.total_latencies.samplecount (count) |
Sample Count of latency calculated from request received by proxy until proxy sees ACK from client on last response byte. shown as millisecond |
|
gcp.loadbalancing.https.total_latencies.sumsqdev (gauge) |
Sum of Squared Deviation of latency calculated from request received by proxy until proxy sees ACK from client on last response byte. shown as millisecond |
|
gcp.loadbalancing.tcp_ssl_proxy.closed_connections (count) |
Number of connections that were terminated over TCP/SSL proxy. shown as connection |
|
gcp.loadbalancing.tcp_ssl_proxy.egress_bytes_count (count) |
Number of bytes sent from VM to client using proxy. shown as byte |
|
gcp.loadbalancing.tcp_ssl_proxy.frontend_tcp_rtt.avg (gauge) |
Average smoothed RTT measured by the proxy's TCP stack. Each minute application layer bytes pass from proxy to client. shown as millisecond |
|
gcp.loadbalancing.tcp_ssl_proxy.frontend_tcp_rtt.samplecount (count) |
Sample count of smoothed RTT measured by the proxy's TCP stack. Each minute application layer bytes pass from proxy to client. shown as millisecond |
|
gcp.loadbalancing.tcp_ssl_proxy.frontend_tcp_rtt.sumsqdev (gauge) |
Sum of squared deviation of smoothed RTT measured by the proxy's TCP stack. Each minute application layer bytes pass from proxy to client. shown as millisecond |
|
gcp.loadbalancing.tcp_ssl_proxy.ingress_bytes_count (count) |
Number of bytes sent from client to VM using proxy. shown as byte |
|
gcp.loadbalancing.tcp_ssl_proxy.new_connections (count) |
Number of connections that were created over TCP/SSL proxy. shown as connection |
|
gcp.loadbalancing.tcp_ssl_proxy.open_connections (count) |
Current number of outstanding connections through the TCP/SSL proxy. shown as connection |
|
gcp.interconnect.network.attachment.received_bytes_count (count) |
Number of inbound bytes received. shown as byte |
|
gcp.interconnect.network.attachment.received_packets_count (count) |
Number of inbound packets received. shown as packet |
|
gcp.interconnect.network.attachment.sent_bytes_count (count) |
Number of outbound bytes sent. shown as byte |
|
gcp.interconnect.network.attachment.sent_packets_count (count) |
Number of outbound packets sent. shown as packet |
|
gcp.interconnect.network.interconnect.capacity (gauge) |
Active capacity of the interconnect. shown as byte |
|
gcp.interconnect.network.interconnect.dropped_packets_count (count) |
Number of outbound packets dropped due to link congestion. shown as packet |
|
gcp.interconnect.network.interconnect.link.operational (gauge) |
Whether the operational status of the circuit is up. |
|
gcp.interconnect.network.interconnect.link.rx_power (gauge) |
Light level received over physical circuit. |
|
gcp.interconnect.network.interconnect.link.tx_power (gauge) |
Light level transmitted over physical circuit. |
|
gcp.interconnect.network.interconnect.operational (gauge) |
Whether the operational status of the interconnect is up. |
|
gcp.interconnect.network.interconnect.receive_errors_count (count) |
Number of errors encountered while receiving packets. shown as error |
|
gcp.interconnect.network.interconnect.received_bytes_count (count) |
Number of inbound bytes received. shown as byte |
|
gcp.interconnect.network.interconnect.received_unicast_packets_count (count) |
Number of inbound unicast packets received. shown as packet |
|
gcp.interconnect.network.interconnect.send_errors_count (count) |
Number of errors encountered while sending packets. shown as error |
|
gcp.interconnect.network.interconnect.sent_bytes_count (count) |
Number of outbound bytes sent. shown as byte |
|
gcp.interconnect.network.interconnect.sent_unicast_packets_count (count) |
Number of outbound unicast packets sent. shown as packet |
All service events generated by your Google Cloud Platform are forwarded to your Datadog event stream. Other events captured in Stackdriver are not currently available but will be in the future with the Datadog Log management product.
The Google Cloud Platform integration does not include any service check at this time.
For non-standard gcp.logging metrics (i.e. metrics beyond our out of the box logging metrics), the metadata we apply may not be consistent with Stackdriver.
In these cases, the metadata should be manually set by navigating to the metric summary page, searching and selecting the metric in question, and clicking the Pencil icon next to metadata.
Need help? Contact Datadog Support.
Tags are automatically assigned based on a variety of configuration options with regards to Google Cloud Platform and the Google Compute Engine. The following tags will be automatically assigned:
Also, any hosts with <key>:<value> labels get tagged with them.