Choosing an Instrumentation Method for Containers

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

To instrument your Google Cloud Run containers with Datadog, choose one of two options:

In-Process
Sidecar

  • In-process: Wraps your application container with the Datadog Agent. Choose this option for a simpler setup, lower cost overhead, and direct log piping.
  • Sidecar: Deploys the Datadog Agent in a separate container alongside your app container. Choose this option if you have multiple containers in a single service, if you prefer strict isolation of the Datadog Agent, or if you have performance-sensitive workloads.

Comparison: in-process versus sidecar instrumentation

AspectIn-processSidecar
DeploymentOne container (your app, wrapped with the Datadog Agent)Two containers ( your app, Datadog Agent)
Image changesIncreases app image size.No change to app image.
Cost overheadLess than sidecar (no extra container).Extra vCPU/memory. Overallocating the sidecar wastes cost; underallocating leads to premature scaling.
LoggingDirect stdout/stderr access.Shared volume + log library routing to a log file. Uncaught errors require extra handling, since they are not automatically handled by your logging library.
Failure isolationIn rare cases, Datadog Agent bugs can affect your app.Datadog Agent faults are isolated.
Observing multiple containersNot supportedSupported

Further reading

Documentation, liens et articles supplémentaires utiles:

Google Cloud Run IntegrationDOCUMENTATION more more Collect traces, logs, and custom metrics from Cloud Run servicesBLOG more more Instrument your container with the in-process approachDOCUMENTATION more more Instrument your container with the sidecar approachDOCUMENTATION more more