설정

1. Datadog Node.js SDK를 설치합니다.

   1. 메인 애플리케이션에서 dd-trace 패키지를 설치합니다.

      Copy

      npm install dd-trace

   2. Node.js 트레이서를 NODE_OPTIONS 환경 변수로 초기화합니다.

      Copy

      ENV NODE_OPTIONS="--require dd-trace/init"

   자세한 내용은 Node.js 애플리케이션 트레이싱을 참조하세요.

2. serverless-init을 설치합니다.

   Datadog publishes new releases of the serverless-init container image to Google’s gcr.io, AWS’s ECR, and on Docker Hub:

   hub.docker.com	gcr.io	public.ecr.aws
   datadog/serverless-init	gcr.io/datadoghq/serverless-init	public.ecr.aws/datadog/serverless-init

   Images are tagged based on semantic versioning, with each new version receiving three relevant tags:

   • 1, 1-alpine: use these to track the latest minor releases, without breaking changes
   • 1.x.x, 1.x.x-alpine: use these to pin to a precise version of the library
   • latest, latest-alpine: use these to follow the latest version release, which may include breaking changes

   Add the following instructions and arguments to your Dockerfile.

   COPY --from=datadog/serverless-init:<YOUR_TAG> /datadog-init /app/datadog-init
   ENTRYPOINT ["/app/datadog-init"]
   CMD ["/nodejs/bin/node", "/path/to/your/app.js"]
   

   Alternative configuration

   Datadog expects serverless-init to be the top-level application, with the rest of your app’s command line passed in for serverless-init to execute.

   If you already have an entrypoint defined inside your Dockerfile, you can instead modify the CMD argument.

   CMD ["/app/datadog-init", "/nodejs/bin/node", "/path/to/your/app.js"]
   

   If you require your entrypoint to be instrumented as well, you can instead swap your entrypoint and CMD arguments.

   ENTRYPOINT ["/app/datadog-init"]
   CMD ["/your_entrypoint.sh", "/nodejs/bin/node", "/path/to/your/app.js"]
   

   As long as your command to run is passed as an argument to datadog-init, you will receive full instrumentation.

   
   

3. 로그를 설정합니다.

   로깅을 활성화하려면 DD_LOGS_ENABLED=true 환경 변수를 설정합니다. 이렇게 하면 serverless-init이 stdout 및 stderr에서 로그를 읽을 수 있습니다.

   Datadog은 고급 Datadog 로그 구문 분석을 활성화하기 위해 환경 변수 DD_LOGS_INJECTION=true 및 DD_SOURCE=nodejs를 설정할 것을 권장합니다.

   줄이 여러 개인 로그를 로그 메시지 하나에 보존하고자 하는 경우, 로그를 JSON 형식으로 쓰는 것이 좋습니다. 예를 들어 winston과 같은 타사 로깅 라이브러리를 사용할 수 있습니다.

   Copy

   const { createLogger, format, transports } = require('winston');
   
   const logger = createLogger({
     level: 'info',
     exitOnError: false,
     format: format.json(),
     transports: [
       new transports.Console()
     ],
   });
   
   logger.info('Hello world!');

   자세한 내용은 Node.js 로그 및 트레이스 상관관계 수립을 참조하세요.

4. 애플리케이션을 구성합니다.

   After the container is built and pushed to your registry, set the required environment variables for the Datadog Agent:

   • DD_API_KEY: Your Datadog API key, used to send data to your Datadog account. For privacy and safety, configure this API key as a Google Cloud Secret.
   • DD_SITE: Your Datadog site. For example, datadoghq.com.

   For more environment variables, see the Environment variables section on this page.

   The following command deploys the service and allows any external connection to reach it. In this example, your service listening is set to port 8080. Ensure that this port number matches the exposed port inside of your Dockerfile.

   gcloud run deploy <APP_NAME>
     --image=gcr.io/<YOUR_PROJECT>/<APP_NAME> \
     --port=8080 \
     --update-env-vars=DD_API_KEY=$DD_API_KEY \
     --update-env-vars=DD_SITE=$DD_SITE \
   

5. Add a service label in Google Cloud. In your Cloud Run service’s info panel, add a label with the following key and value:

   Key	Value
   service	The name of your service. Matches the value provided as the DD_SERVICE environment variable.

   See Configure labels for services in the Cloud Run documentation for instructions.

6. 커스텀 메트릭을 전송합니다.

   커스텀 메트릭을 전송하려면 코드 예시를 참고하세요. 서버리스에서는 분포 메트릭 유형만 지원됩니다.

7. 프로파일링을 활성화합니다(미리 보기).

   Continuous Profiler를 활성화하려면 환경 변수 DD_PROFILING_ENABLED=true를 설정합니다.

   Datadog의 Continuous Profiler는 Google Cloud Run 서비스에서 미리 보기로 제공됩니다.

Environment variables

Do not set the following environment variables in your serverless environment. They should only be set in non-serverless environments.

• DD_AGENT_HOST
• DD_TRACE_AGENT_URL

Pub/Sub을 사용한 분산 추적

To get end-to-end distributed traces between Pub/Sub producers and Cloud Run, configure your push subscriptions with the --push-no-wrapper and --push-no-wrapper-write-metadata flags. This moves message attributes from the JSON body to HTTP headers, allowing Datadog to extract producer trace context and create span links.

For more information, see Producer-aware tracing for Google Cloud Pub/Sub and Cloud Run and Payload unwrapping in the Google Cloud documentation.

Configure push subscriptions for full trace visibility

Create a new push subscription:

gcloud pubsub subscriptions create order-processor-sub \
  --topic=orders \
  --push-endpoint=https://order-processor-xyz.run.app/pubsub \
  --push-no-wrapper \
  --push-no-wrapper-write-metadata

Update an existing push subscription:

gcloud pubsub subscriptions update order-processor-sub \
  --push-no-wrapper \
  --push-no-wrapper-write-metadata

Configure Eventarc Pub/Sub triggers

Eventarc Pub/Sub triggers use push subscriptions as the underlying delivery mechanism. When you create an Eventarc trigger, GCP automatically creates a managed push subscription. However, Eventarc does not expose --push-no-wrapper-write-metadata as a trigger creation parameter, so you must manually update the auto-created subscription.

1. Create the Eventarc trigger:

   gcloud eventarc triggers create order-processor-trigger \
     --destination-run-service=order-processor \
     --destination-run-region=us-central1 \
     --event-filters="type=google.cloud.pubsub.topic.v1.messagePublished" \
     --transport-topic=projects/my-project/topics/orders \
     --location=us-central1
   

2. Find the auto-created subscription:

   gcloud pubsub subscriptions list \
     --filter="topic:projects/my-project/topics/orders" \
     --format="table(name,pushConfig.pushEndpoint)"
   

   Example output:

   NAME                                                          PUSH_ENDPOINT
   eventarc-us-central1-order-processor-trigger-abc-sub-def      https://order-processor-xyz.run.app
   

3. Update the subscription for trace propagation:

   gcloud pubsub subscriptions update \
     eventarc-us-central1-order-processor-trigger-abc-sub-def \
     --push-no-wrapper \
     --push-no-wrapper-write-metadata
   

문제 해결

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.

If you are using request-based billing for a Google Cloud Run application instrumented in-container, very short requests may lead to dropped logs during the post-request CPU throttling. You can control the speed at which logs are sent to Datadog using the DD_LOGS_CONFIG_BATCH_WAIT environment variable. Set DD_LOGS_CONFIG_BATCH_WAIT to a value shorter than your typical request duration to avoid dropped logs. Sidecar instrumentation also prevents this issue, as the sidecar is not affected by request-based CPU throttling.

추가 자료

추가적인 유용한 설명서, 링크 및 기사:

Node.js 애플리케이션 트레이싱설명서 Node.js 로그 및 트레이스 상관관계 수립설명서