Google Cloud Run for Anthos
Présentation
Google Cloud Run for Anthos est une plateforme flexible de développement sans serveur pour les environnements hybrides et multicloud. Cloud Run for Anthos est l’offre Knative gérée par Google et entièrement compatible.
Utilisez l’intégration Datadog/Google Cloud Platform pour recueillir des métriques de Google Cloud Run for Anthos.
Configuration
Collecte de métriques
Installation
Si vous ne l’avez pas déjà fait, configurez d’abord l’intégration Google Cloud Platform.
Si vous authentifiez déjà vos services Cloud Run for Anthos à l’aide de Workload Identity, aucune étape supplémentaire n’est requise.
Si vous n’avez pas activé Workload Identity, vous devez adopter Workload Identity afin de commencer à recueillir des métriques Knative. Pour y parvenir, vous devez lier un compte de service Kubernetes à un compte de service Google et configurer Workload Identity pour chaque service à partir duquel vous souhaitez recueillir des métriques.
Pour obtenir des instructions de configuration détaillées, consultez la section Utiliser Workload Identity de la documentation Google Cloud.
Collecte de logs
Google Cloud Run for Anthos expose des logs de service. Les logs Google Cloud Run peuvent être recueillis avec Google Cloud Logging 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 Google Cloud Run depuis Google Cloud Logging vers le Pub/Sub :
Accédez à Cloud Run for Anthos, cliquez sur les services de votre choix, puis accédez à l’onglet Logs.
Cliquez sur View in Logs Explorer pour accéder à la page Google Cloud Logging.
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 attendez que le message de confirmation s’affiche.
Données collectées
Métriques
gcp.knative.eventing.broker.event_count
(count) | Number of events received by a broker. |
gcp.knative.eventing.trigger.event_count
(count) | Number of events received by a trigger. |
gcp.knative.eventing.trigger.event_dispatch_latencies.avg
(gauge) | Average of time spent dispatching an event to a trigger subscriber.
Shown as millisecond |
gcp.knative.eventing.trigger.event_dispatch_latencies.p99
(gauge) | 99th percentile of time spent dispatching an event to a trigger subscriber.
Shown as millisecond |
gcp.knative.eventing.trigger.event_dispatch_latencies.p95
(gauge) | 95th percentile of time spent dispatching an event to a trigger subscriber.
Shown as millisecond |
gcp.knative.eventing.trigger.event_processing_latencies.avg
(gauge) | Average of time spent processing an event before it is dispatched to a trigger subscriber.
Shown as millisecond |
gcp.knative.eventing.trigger.event_processing_latencies.p99
(gauge) | 99th percentile of time spent processing an event before it is dispatched to a trigger subscriber.
Shown as millisecond |
gcp.knative.eventing.trigger.event_processing_latencies.p95
(gauge) | 95th percentile of time spent processing an event before it is dispatched to a trigger subscriber.
Shown as millisecond |
gcp.knative.serving.activator.request_count
(count) | The number of requests that are routed to the activator.
Shown as request |
gcp.knative.serving.activator.request_latencies.avg
(gauge) | Average of service request times in milliseconds for requests that go through the activator.
Shown as millisecond |
gcp.knative.serving.activator.request_latencies.p99
(gauge) | 99th percentile of service request times in milliseconds for requests that go through the activator.
Shown as millisecond |
gcp.knative.serving.activator.request_latencies.p95
(gauge) | 95th percentile of service request times in milliseconds for requests that go through the activator.
Shown as millisecond |
gcp.knative.serving.autoscaler.actual_pods
(gauge) | Number of pods that are allocated currently. |
gcp.knative.serving.autoscaler.desired_pods
(gauge) | Number of pods autoscaler wants to allocate. |
gcp.knative.serving.autoscaler.panic_mode
(gauge) | Set to 1 if autoscaler is in panic mode for the revision, otherwise 0. |
gcp.knative.serving.autoscaler.panic_request_concurrency
(gauge) | Average requests concurrency observed per pod during the shorter panic autoscaling window.
Shown as request |
gcp.knative.serving.autoscaler.requested_pods
(gauge) | Number of pods autoscaler requested from Kubernetes. |
gcp.knative.serving.autoscaler.stable_request_concurrency
(gauge) | Average requests concurrency observed per pod during the stable autoscaling window.
Shown as request |
gcp.knative.serving.autoscaler.target_concurrency_per_pod
(gauge) | The desired average requests concurrency per pod during the stable autoscaling window.
Shown as request |
gcp.knative.serving.revision.request_count
(count) | The number of requests reaching the revision.
Shown as request |
gcp.knative.serving.revision.request_latencies.avg
(gauge) | Average of service request times in milliseconds for requests reaching the revision.
Shown as millisecond |
gcp.knative.serving.revision.request_latencies.p99
(gauge) | 99th percentile of service request times in milliseconds for requests reaching the revision.
Shown as millisecond |
gcp.knative.serving.revision.request_latencies.p95
(gauge) | 95th percentile of service request times in milliseconds for requests reaching the revision.
Shown as millisecond |
Événements
L’intégration Google Cloud Run for Anthos n’inclut aucun événement.
Checks de service
L’intégration Google Cloud Run for Anthos n’inclut aucun check de service.
Dépannage
Besoin d’aide ? Contactez l’assistance Datadog.
Pour aller plus loin
Documentation, liens et articles supplémentaires utiles:
