1. If you have not already, install the Datadog CLI v2.18.0+.

   npm install -g @datadog/datadog-ci
   

   Copy

2. Ensure you have deployed the Datadog Lambda Forwarder, 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.

   Take note of your Forwarder’s ARN.

3. Instrument your Step Function.

   datadog-ci stepfunctions instrument \
    --step-function <STEP_FUNCTION_ARN> \
    --forwarder <FORWARDER_ARN> \
    --env <ENVIRONMENT> \
    --propagate-upstream-trace
   

   Copy
   • Replace <STEP_FUNCTION_ARN> with the ARN of your Step Function. Repeat the --step-function flag for each Step Function you wish to instrument.
   • Replace <FORWARDER_ARN> with the ARN of your Datadog Lambda Forwarder, as noted previously.
   • Replace <ENVIRONMENT> with the environment tag you would like to apply to your Step Functions.
   • --propagate-upstream-trace is optional, and updates your Step Function definitions to inject Step Function context into any downstream Step Function or Lambda invocations.

   For more information about the datadog-ci stepfunctions command, see the Datadog CLI documentation.

4. For Node.js and Python runtimes, add the flag --merge-step-function-and-lambda-traces in your datadog-ci command. This links your Step Function traces with Lambda traces. If you have not yet instrumented your Lambda functions to send traces, you can follow the steps to add the Lambda layer for your preferred runtime.

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.

2. Ensure you have deployed the Datadog Lambda Forwarder, 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. 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.

3. Subscribe CloudWatch logs to the Datadog Lambda Forwarder. To do this, you have two options:

   • Datadog-AWS integration (recommended)

     1. Ensure that you have set up the Datadog-AWS integration.
     2. In Datadog, open the AWS integration tile, and view the Configuration tab.
     3. On the left, select the AWS account where your Step Function is running. Open the Log Collection tab.
     4. In the Log Autosubscription section, under Autosubscribe Forwarder Lambda Functions, enter the ARN of your Datadog Lambda Forwarder, as noted previously. Click Add.
     5. Toggle on Step Functions CloudWatch Logs. Changes take 15 minutes to take effect.

     Note: Log Autosubscription requires your Lambda Forwarder and Step Function to be in the same region.

   • Manual

     1. Ensure that your log group name has the prefix /aws/vendedlogs/states.
     2. Open your AWS console and go to your Datadog Lambda Forwarder. In the Function overview section, click on Add trigger.
     3. Under Add trigger, in the Trigger configuration section, use the Select a source dropdown to select CloudWatch Logs.
     4. Under Log group, select the log group for your state machine. For example, /aws/vendedlogs/states/my-state-machine.
     5. Enter a filter name. You can choose to name it “empty filter” and leave the Filter pattern box blank.

4. Set up tags. Open your AWS console and go to your Step Functions state machine. Open the Tags section and add env:<ENV_NAME>, service:<SERVICE_NAME>, and version:<VERSION> 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. The version tag defaults to 1.0.

5. 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:

   "Parameters": {
     "Payload.$": "States.JsonMerge($$, $, false)",
     ...
   }
   

   Copy

   The JsonMerge intrinsic function merges the Step Functions context object ($$) with the original Lambda’s input payload ($). Fields of the original payload overwrite the Step Functions context object if their keys are the same.

Example:

"Lambda Read From DynamoDB": {
      "Type": "Task",
      "Resource": "arn:aws:states:::lambda:invoke",
      "Parameters": {
        "Payload.$": "States.JsonMerge($$, $, false)",
        "FunctionName": "${lambdaArn}"
      },
      "End": true
    }

Alternatively, if you have business logic defined in the payload, you could also use the following:

"Lambda Read From DynamoDB": {
      "Type": "Task",
      "Resource": "arn:aws:states:::lambda:invoke",
      "Parameters": {
        "Payload": {
          ...
          "Execution.$": "$$.Execution",
          "State.$": "$$.State",
          "StateMachine.$": "$$.StateMachine"
        },
        "FunctionName": "${lambdaArn}"
      },
      "End": true
    }

If you have not yet instrumented your Lambda functions to send traces, you can follow the steps to add the Lambda layer for your preferred runtime.