From 02db20ac0bf4e9afbbd18c47029cb7896b8db718 Mon Sep 17 00:00:00 2001 From: Abhinav Vedmala Date: Wed, 31 Jul 2024 15:58:39 -0400 Subject: [PATCH 1/4] Enable step function tracing at forwarder level --- content/en/serverless/step_functions/installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/serverless/step_functions/installation.md b/content/en/serverless/step_functions/installation.md index 54d38ecb68304..4556ecf955b81 100644 --- a/content/en/serverless/step_functions/installation.md +++ b/content/en/serverless/step_functions/installation.md @@ -102,7 +102,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications 1. Enable all logging for your Step Function. In your AWS console, open your state machine. Click *Edit* and find the Logging section. There, set *Log level* to `ALL` and enable the *Include execution data* checkbox. {{< img src="serverless/step_functions/aws_log.png" alt="AWS UI, Logging section, showing log level set to ALL." style="width:100%;" >}} -2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. +2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder, you can also set the `DdStepFunctionTraceEnabled` parameter in CloudFormation to `true` to enable tracing for all your Step Functions. Take note of your Forwarder's ARN. @@ -126,7 +126,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications
If you are using a different instrumentation method such as Serverless Framework or datadog-ci, enabling autosubscription may create duplicated logs. Choose one configuration method to avoid this behavior..
4. Enable enhanced metrics on your Step Function by adding a `DD_ENHANCED_METRICS` tag. Set the value to `true`. -5. Enable tracing on your Step Function by adding a `DD_TRACE_ENABLED` tag. Set the value to `true`. +5. Enable tracing on your Step Function by adding a `DD_TRACE_ENABLED` tag. Set the value to `true`. This is only needed if `DD_STEP_FUNCTION_TRACE_ENABLED` hasn't been set by the Forwarder. 6. Set up tags. Open your AWS console and go to your Step Functions state machine. Open the *Tags* section and add `env:` and `service:` tags. The `env` tag is required to see traces in Datadog, and it defaults to `dev`. The `service` tag defaults to the state machine's name. 7. For Node.js and Python runtimes, you can link your Step Function traces to Lambda traces. On the Lambda Task, set the `Parameters` key with the following: From e76b5f1c591e7318584f1124422a9edcdebcd74b Mon Sep 17 00:00:00 2001 From: Abhinav Vedmala Date: Wed, 31 Jul 2024 16:45:03 -0400 Subject: [PATCH 2/4] updated language to mention forwarder-level --- content/en/serverless/step_functions/installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/serverless/step_functions/installation.md b/content/en/serverless/step_functions/installation.md index 4556ecf955b81..858ad2a4ca816 100644 --- a/content/en/serverless/step_functions/installation.md +++ b/content/en/serverless/step_functions/installation.md @@ -102,7 +102,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications 1. Enable all logging for your Step Function. In your AWS console, open your state machine. Click *Edit* and find the Logging section. There, set *Log level* to `ALL` and enable the *Include execution data* checkbox. {{< img src="serverless/step_functions/aws_log.png" alt="AWS UI, Logging section, showing log level set to ALL." style="width:100%;" >}} -2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder, you can also set the `DdStepFunctionTraceEnabled` parameter in CloudFormation to `true` to enable tracing for all your Step Functions. +2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder, you can also set the `DdStepFunctionTraceEnabled` parameter in CloudFormation to enable tracing for all your Step Functions at the Forwarder-level. Take note of your Forwarder's ARN. From f78e1e905efb6f086582383d64d49dbd97d4fed9 Mon Sep 17 00:00:00 2001 From: Abhinav Vedmala Date: Thu, 1 Aug 2024 12:58:11 -0400 Subject: [PATCH 3/4] Added 's' to make it 'StepFunctions' --- content/en/serverless/step_functions/installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/serverless/step_functions/installation.md b/content/en/serverless/step_functions/installation.md index 858ad2a4ca816..6e31a3b33d99e 100644 --- a/content/en/serverless/step_functions/installation.md +++ b/content/en/serverless/step_functions/installation.md @@ -102,7 +102,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications 1. Enable all logging for your Step Function. In your AWS console, open your state machine. Click *Edit* and find the Logging section. There, set *Log level* to `ALL` and enable the *Include execution data* checkbox. {{< img src="serverless/step_functions/aws_log.png" alt="AWS UI, Logging section, showing log level set to ALL." style="width:100%;" >}} -2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder, you can also set the `DdStepFunctionTraceEnabled` parameter in CloudFormation to enable tracing for all your Step Functions at the Forwarder-level. +2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder, you can also set the `DdStepFunctionsTraceEnabled` parameter in CloudFormation to enable tracing for all your Step Functions at the Forwarder-level. Take note of your Forwarder's ARN. @@ -126,7 +126,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications
If you are using a different instrumentation method such as Serverless Framework or datadog-ci, enabling autosubscription may create duplicated logs. Choose one configuration method to avoid this behavior..
4. Enable enhanced metrics on your Step Function by adding a `DD_ENHANCED_METRICS` tag. Set the value to `true`. -5. Enable tracing on your Step Function by adding a `DD_TRACE_ENABLED` tag. Set the value to `true`. This is only needed if `DD_STEP_FUNCTION_TRACE_ENABLED` hasn't been set by the Forwarder. +5. Enable tracing on your Step Function by adding a `DD_TRACE_ENABLED` tag. Set the value to `true`. This is only needed if `DD_STEP_FUNCTIONS_TRACE_ENABLED` hasn't been set by the Forwarder. 6. Set up tags. Open your AWS console and go to your Step Functions state machine. Open the *Tags* section and add `env:` and `service:` tags. The `env` tag is required to see traces in Datadog, and it defaults to `dev`. The `service` tag defaults to the state machine's name. 7. For Node.js and Python runtimes, you can link your Step Function traces to Lambda traces. On the Lambda Task, set the `Parameters` key with the following: From 0b4768e40db177c8f6ca534b3314eabd6e7f4c83 Mon Sep 17 00:00:00 2001 From: Abhinav Vedmala Date: Mon, 5 Aug 2024 10:19:51 -0400 Subject: [PATCH 4/4] Added version number --- content/en/serverless/step_functions/installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/serverless/step_functions/installation.md b/content/en/serverless/step_functions/installation.md index 6e31a3b33d99e..972cb3aa0db02 100644 --- a/content/en/serverless/step_functions/installation.md +++ b/content/en/serverless/step_functions/installation.md @@ -102,7 +102,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications 1. Enable all logging for your Step Function. In your AWS console, open your state machine. Click *Edit* and find the Logging section. There, set *Log level* to `ALL` and enable the *Include execution data* checkbox. {{< img src="serverless/step_functions/aws_log.png" alt="AWS UI, Logging section, showing log level set to ALL." style="width:100%;" >}} -2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder, you can also set the `DdStepFunctionsTraceEnabled` parameter in CloudFormation to enable tracing for all your Step Functions at the Forwarder-level. +2. Ensure you have deployed the [Datadog Lambda Forwarder][1], a Lambda function that ships logs from AWS to Datadog, and that you are using v3.74.0+. You may need to [update your Forwarder][2]. When deploying the Forwarder on v3.121.0+, you can also set the `DdStepFunctionsTraceEnabled` parameter in CloudFormation to enable tracing for all your Step Functions at the Forwarder-level. Take note of your Forwarder's ARN. @@ -126,7 +126,7 @@ For developers using [Serverless Framework][4] to deploy serverless applications
If you are using a different instrumentation method such as Serverless Framework or datadog-ci, enabling autosubscription may create duplicated logs. Choose one configuration method to avoid this behavior..
4. Enable enhanced metrics on your Step Function by adding a `DD_ENHANCED_METRICS` tag. Set the value to `true`. -5. Enable tracing on your Step Function by adding a `DD_TRACE_ENABLED` tag. Set the value to `true`. This is only needed if `DD_STEP_FUNCTIONS_TRACE_ENABLED` hasn't been set by the Forwarder. +5. Enable tracing on your Step Function by adding a `DD_TRACE_ENABLED` tag. Set the value to `true`. This is only needed if `DD_STEP_FUNCTIONS_TRACE_ENABLED` hasn't been set by the Forwarder. 6. Set up tags. Open your AWS console and go to your Step Functions state machine. Open the *Tags* section and add `env:` and `service:` tags. The `env` tag is required to see traces in Datadog, and it defaults to `dev`. The `service` tag defaults to the state machine's name. 7. For Node.js and Python runtimes, you can link your Step Function traces to Lambda traces. On the Lambda Task, set the `Parameters` key with the following: