Datadog-Google Cloud Platform Integration

Overview

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 Engineplatform as a service to build scalable applications
Big Queryenterprise data warehouse
CloudSQLMySQL database service
Compute Enginehigh performance virtual machines
Container Enginekubernetes, managed by google
DatastoreNoSQL database
Firebasemobile platform for application development
FunctionsA serverless platform for building event-based microservices
Machine Learningmachine learning services
Pub/Subreal-time messaging service
Spannerhorizontally scalable, globally consistent, relational database service
Stackdriver Loggingreal-time log management and analysis
Storageunified object storage
VPNmanaged network functionality

Setup

Installation

From the Integrations page in the Datadog app, select the Google Cloud Platform tile. Switch to the Configuration tab and click the Sign in with Google button. After you allow access enter the email associated with the account and the Project you wish to monitor. Enter the Project ID for each project. The Project ID is the multi-word id and not the Project Number.

To configure the GCP integration, you need these permissions:

https://www.googleapis.com/auth/compute.readonly
https://www.googleapis.com/auth/monitoring.read

Also, billing must be enbled for the account(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.*
settings

Data Collected

Metrics

gcp.loadbalancing.http.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.http.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.http.backend_latencies.max
(gauge)
Maximum latency of request sent by the proxy to backend until proxy receives last byte of response from backend.
shown as millisecond
gcp.loadbalancing.http.backend_latencies.min
(gauge)
Minimum latency of request sent by the proxy to backend until proxy receives last byte of response from backend.
shown as millisecond
gcp.loadbalancing.http.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.http.frontend_tcp_rtt.avg
(gauge)
Average RTT for each connection between client and proxy.
shown as millisecond
gcp.loadbalancing.http.frontend_tcp_rtt.samplecount
(count)
Sample Count of RTT for each connection between client and proxy.
shown as millisecond
gcp.loadbalancing.http.frontend_tcp_rtt.max
(gauge)
Maximum RTT for each connection between client and proxy.
shown as millisecond
gcp.loadbalancing.http.frontend_tcp_rtt.min
(gauge)
Minimum RTT for each connection between client and proxy.
shown as millisecond
gcp.loadbalancing.http.frontend_tcp_rtt.sumsqdev
(gauge)
Sum of Squared Deviation of RTT for each connection between client and proxy.
shown as millisecond
gcp.loadbalancing.http.request_bytes_count
(count)
Bytes sent as requests from clients to L7 load balancer.
shown as byte
gcp.loadbalancing.http.request_count
(count)
Number of requests served by L7 load balancer.
shown as request
gcp.loadbalancing.http.response_bytes_count
(count)
Bytes sent as responses from L7 load balancer to clients.
shown as byte
gcp.loadbalancing.http.response_code_class_percentage
(gauge)
Per response code class percentage of total responses by proxy to clients.
shown as percent
gcp.loadbalancing.http.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.http.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.http.total_latencies.max
(gauge)
Maximum latency calculated from request received by proxy until proxy sees ACK from client on last response byte.
shown as millisecond
gcp.loadbalancing.http.total_latencies.min
(gauge)
Minimum latency calculated from request received by proxy until proxy sees ACK from client on last response byte.
shown as millisecond
gcp.loadbalancing.http.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.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.
shown as
gcp.interconnect.network.interconnect.link.rx_power
(gauge)
Light level received over physical circuit.
shown as
gcp.interconnect.network.interconnect.link.tx_power
(gauge)
Light level transmitted over physical circuit.
shown as
gcp.interconnect.network.interconnect.operational
(gauge)
Whether the operational status of the interconnect is up.
shown as
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

Further Reading

Knowledge Base

Tags Assigned

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:

  • Zone
  • Instance-type
  • Instance-id
  • Automatic-restart
  • On-host-maintenance
  • Project
  • Numeric_project_id
  • Name

Also, any hosts with <key>:<value> labels get tagged with them.