[SVLS-7874] update documentaiton for serverless deployment tracking (#32928)

* [SVLS-7874] update documentaiton for serverless deployment tracking

* Update content/en/serverless/aws_lambda/deployment_tracking.md

Co-authored-by: Joe Peeples <[email protected]>

---------

Co-authored-by: Joe Peeples <[email protected]>

Author: jchrostek-dd

content/en/serverless/aws_lambda/deployment_tracking.md

@@ -13,13 +13,13 @@ aliases:
 
 Deployment tracking helps you to understand when a new version of code or a configuration change causes a spike in errors, degraded performance, or when your cloud environment drifts from its expected state.
 
-To access deployment tracking for your serverless applications, select a function in the [Serverless view][1] to open a side panel, and click the **Deployments** tab. This shows key serverless metrics like invocations, execution duration, and error counts automatically displayed with event overlays that mark code deployments and configuration changes related to the function.
+## Deployment Events
 
-For visibility into historical code and configuration changes, adjust the global time selector at the top right of the view.
+Datadog collects code and configuration change events for your AWS Lambda functions from AWS CloudTrail.
 
-## Setup
+To see deployment events for your serverless applications, select a function in the [Serverless view][1] to open a side panel, and click the **Deployments** tab.
 
-Datadog collects code and configuration change events for your AWS Lambda functions from AWS CloudTrail.
+### Setup
 
 1. If you haven't already, set up the [Amazon Web Services][2] integration. 
 
@@ -33,7 +33,7 @@ If you have already added the permission, but you still don't see events for any
 
 {{< img src="serverless/lambda_integration_settings.png" alt="Lambda Integration Settings" style="width:100%;">}}
 
-### Resource Changes
+## Resource Changes
 
 <div class="alert alert-info">Resource Changes is in Preview. Enabling resource collection can impact your AWS CloudWatch costs.</div>
 
@@ -45,6 +45,17 @@ You can use [Resource Changes][4] for visibility and control over configuration
 
 See the [Resource Changes][4] documentation for more information.
 
+## Tag telemetry with deployment information
+
+Datadog can group your metrics by tags such as `git.commit.sha` to correlate code changes with issues.
+
+{{< img src="serverless/metrics_grouped_by_git_commit.png" alt="Metrics Grouped By Git Commit" style="width:100%;">}}
+
+Depending on your configuration, the Datadog Lambda Extension adds the following tags to your metrics, logs, and traces:
+- `executed_version`: The AWS Lambda function version that was executed. This tag is added by the Datadog Lambda Extension when you enable [AWS Lambda versioning][6] for your function. To use this feature, you must publish versions of your Lambda function and configure aliases or direct invocations to use specific versions.
+- `version`: The deployment version tag set through the `DD_VERSION` Lambda environment variable. If you have this as an environment variable, it is added as a tag by the Datadog Lambda Extension.
+- `git.commit.sha`: The Git commit hash associated with the deployed code. This must be included in the `DD_TAGS` Lambda environment variable (for example, `DD_TAGS=git.commit.sha:abc123def456`). If you deploy your Lambda function using Datadog's CI or CDK construct, this tag is automatically added to the `DD_TAGS` environment variable during deployment. Otherwise, you must add it to `DD_TAGS` yourself.
+
 ## Further Reading
 
 {{< partial name="whats-next/whats-next.html" >}}
@@ -53,4 +64,5 @@ See the [Resource Changes][4] documentation for more information.
 [2]: /integrations/amazon_web_services/#setup
 [3]: https://app.datadoghq.com/integrations/amazon-lambda
 [4]: /infrastructure/resource_catalog/resource_changes/
-[5]: https://app.datadoghq.com/integrations/amazon-web-services
+[5]: https://app.datadoghq.com/integrations/amazon-web-services
+[6]: https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html