Google Cloud Load Balancing vous permet de répartir vos ressources informatiques à équilibrage de charge dans une seule ou plusieurs régions, près de vos utilisateurs, et de bénéficier de la haute disponibilité dont vous avez besoin. Associez vos ressources à une seule adresse IP Anycast et faites-les évoluer à la hausse ou à la baisse grâce à la fonctionnalité d’autoscaling intelligent.
Utilisez l’intégration Datadog/Google Cloud Platform pour recueillir des métriques de Google Cloud Load Balancing.
Si vous ne l’avez pas déjà fait, configurez d’abord l’intégration Google Cloud Platform. Aucune autre procédure d’installation n’est requise.
Les logs d’équilibreur de charge HTTP Google Cloud sont recueillis avec Stackdriver et envoyés à un Cloud Pub/Sub via un redirecteur Push HTTP. Si vous ne l’avez pas déjà fait, configurez le Cloud Pub/Sub à l’aide d’un redirecteur Push HTTP.
Une fois cette opération effectuée, exportez vos logs d’équilibreur de charge HTTP Google Cloud depuis Stackdriver vers le Pub/Sub :
Accédez à la page Stackdriver et filtrez les logs d’équilibreur de charge HTTP Google Cloud.
Cliquez sur Create Sink et nommez le récepteur.
Choisissez Cloud Pub/Sub comme destination et sélectionnez le Pub/Sub créé à cette fin. Remarque : le Pub/Sub peut se situer dans un autre projet.
Cliquez sur Create et patientez jusqu’à ce que le message de confirmation apparaisse.
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 sample |
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.backend_request_bytes_count (count) | The number of bytes sent as requests from HTTP/S load balancer to backends. Shown as byte |
gcp.loadbalancing.https.backend_request_count (count) | The number of requests served by backends of HTTP/S load balancer. Shown as request |
gcp.loadbalancing.https.backend_response_bytes_count (count) | The number of bytes sent as responses from backends (or cache) to HTTP/S load balancer. Shown as byte |
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 sample |
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 sample |
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.l3.external.egress_bytes_count (count) | The number of bytes sent from NetLB backend to client of the flow. For TCP flows it's counting bytes on application stream only. Shown as byte |
gcp.loadbalancing.l3.external.egress_packets_count (count) | The number of packets sent from NetLB backend to client of the flow. Shown as packet |
gcp.loadbalancing.l3.external.ingress_bytes_count (count) | The number of bytes sent from client to NetLB backend. For TCP flows it's counting bytes on application stream only. Shown as byte |
gcp.loadbalancing.l3.external.ingress_packets_count (count) | The number of packets sent from client to NetLB backend. Shown as packet |
gcp.loadbalancing.l3.external.rtt_latencies.avg (gauge) | Average RTT measured over TCP connections for NetLB flows. Shown as millisecond |
gcp.loadbalancing.l3.external.rtt_latencies.samplecount (count) | Sample count of RTT measured over TCP connections for NetLB flows. Shown as sample |
gcp.loadbalancing.l3.external.rtt_latencies.sumsqdev (gauge) | Sum of squared deviation for RTT measured over TCP connections for NetLB flows. Shown as millisecond |
gcp.loadbalancing.l3.internal.egress_bytes_count (count) | The number of bytes sent from ILB backend to client (for TCP flows it's counting bytes on application stream only). Shown as byte |
gcp.loadbalancing.l3.internal.egress_packets_count (count) | The number of packets sent from ILB backend to client of the flow. Shown as packet |
gcp.loadbalancing.l3.internal.ingress_bytes_count (count) | The number of bytes sent from client to ILB backend (for TCP flows it's counting bytes on application stream only). Shown as byte |
gcp.loadbalancing.l3.internal.ingress_packets_count (count) | The number of packets sent from client to ILB backend. Shown as packet |
gcp.loadbalancing.l3.internal.rtt_latencies.avg (gauge) | A distribution of RTT measured over TCP connections for ILB flows. Shown as millisecond |
gcp.loadbalancing.l3.internal.rtt_latencies.samplecount (count) | Sample count for RTT latencies Shown as sample |
gcp.loadbalancing.l3.internal.rtt_latencies.sumsqdev (gauge) | Sum of squared deviation for RTT latencies 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 sample |
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 |
L’intégration Google Cloud Load Balancing n’inclut aucun événement.
L’intégration Google Cloud Load Balancing n’inclut aucun check de service.
Besoin d’aide ? Contactez l’assistance Datadog.
Sur cette page