If you are new to Datadog serverless monitoring, launch the Datadog CLI in interactive mode to guide your first installation for a quick start.
datadog-ci cloud-run instrument -i
To permanently install Datadog for your production applications, run the instrument command in your CI/CD pipelines after your normal deployment. You can specify multiple services to instrument by passing multiple --service flags.
After deploying your Cloud Run app, you can manually modify your app’s settings to enable Datadog monitoring.
Create a Volume with In-Memory volume type.
Add a new container with image URL: gcr.io/datadoghq/serverless-init:latest.
Add the volume mount to every container in your application. Choose a path such as /shared-volume, and remember it for the next step. For example:
Add the following environment variables to your serverless-init sidecar container:
DD_SERVICE: A name for your service. For example, gcr-sidecar-test.
DD_ENV: A name for your environment. For example, dev.
DD_SERVERLESS_LOG_PATH: Your log path. For example, /shared-volume/logs/*.log. The path must begin with the mount path you defined in the previous step.
FUNCTION_TARGET: The entry point of your function. For example, Main.
For a list of all environment variables, including additional tags, see Environment variables.
Set up logs.
In the previous step, you created a shared volume. You may have also set the DD_SERVERLESS_LOG_PATH environment variable, which defaults to /shared-volume/logs/app.log.
In this step, configure your logging library to write logs to the file set in DD_SERVERLESS_LOG_PATH. In .NET, Datadog recommends writing logs in JSON format. For example, you can use a third-party logging library such as Serilog:
usingSerilog;conststringLOG_FILE="/shared-volume/logs/app.log";builder.Host.UseSerilog((context,config)=>{// Ensure the directory existsDirectory.CreateDirectory(Path.GetDirectoryName(LOG_FILE)!);config.WriteTo.Console(newSerilog.Formatting.Json.JsonFormatter(renderMessage:true)).WriteTo.File(newSerilog.Formatting.Json.JsonFormatter(renderMessage:true),LOG_FILE);});logger.LogInformation("Hello World!");
Datadog recommends setting the environment variables DD_LOGS_INJECTION=true (in your main container) and DD_SOURCE=csharp (in your sidecar container) to enable advanced Datadog log parsing.
Unless specified otherwise, all environment variables below should be set in the sidecar container. Only environment variables used to configure the tracer should be set in your main application container.
The path where the sidecar should tail logs from. Defaults to /shared-volume/logs/app.log.
DD_LOGS_INJECTION
When true, enrich all logs with trace data for supported loggers. See Correlate Logs and Traces for more information. Set in your main application container, not the sidecar container.
Set the log source to enable a Log Pipeline for advanced parsing. To automatically apply language-specific parsing rules, set to csharp, or use your custom pipeline. Defaults to cloudrun.
DD_TAGS
Add custom tags to your logs, metrics, and traces. Tags should be comma separated in key/value format (for example: key1:value1,key2:value2).
FUNCTION_TARGET
Required for correct tagging. The entry point of your function. For example, Main. You can also find FUNCTION_TARGET on the source tab inside Google console: Function entry point.
Troubleshooting
This integration depends on your runtime having a full SSL implementation. If you are using a slim image, you may need to add the following command to your Dockerfile to include certificates:
RUN apt-get update && apt-get install -y ca-certificates
To have your Cloud Run services appear in the software catalog, you must set the DD_SERVICE, DD_VERSION, and DD_ENV environment variables.
