Change Tracking Feature Flags #29934
Conversation
github-actions
bot
added
Architecture
📝 Documentation Team Review RequiredThis pull request requires approval from the @DataDog/documentation team before it can be merged. Please ensure your changes follow our documentation guidelines and wait for a team member to review and approve your changes. |
Preview links (active after the
|
content/en/change_tracking/_index.md
Outdated
| | SQL Server Database Settings Change | [Database Monitoring (DBM)][8], [Correlate Database Monitoring and Traces][10] | | ||
| | Kafka Schema Updates | [Data Streams Monitoring (DSM)][9] | | ||
| | Manual Kubernetes Deployment Scale Events | Kubernetes Audit Logging | | ||
| | Cloud Infrastructure Resource Changes (AWS, Azure, GCP) | [Resource Changes][13] - Enable Resource Collection and optionally cloud provider event forwarding | |
There was a problem hiding this comment.
@brett0000FF can we denote that this is currently in preview and limited to a small sample of cloud infra resource changes.
Replaced the example request object with the same example from Event Management
| 1. Create a custom span with the operation name `experiments.IsEnabled` to track feature flag evaluations. | ||
| 3. Tag the span with `experiment_id:<flag-id>`, where `<flag-id>` matches the feature flag ID. | ||
|
|
||
| For example: |
There was a problem hiding this comment.
Hey @edcheung24 can you review this example snippet for automatic feature flag detection?
There was a problem hiding this comment.
looks good to me, i added a minor comment to keep things consistent with the example above.
…ion into brett.blue/DOCS-11065
|
Created DOCS-11252 for docs review. |
| ```python | ||
| # Trace feature flag evaluation to enable auto-detection | ||
| with tracer.trace("experiments.IsEnabled") as span: | ||
| span.set_tag("experiment_id", "payment-gateway-flag") |
There was a problem hiding this comment.
perhaps update payment-gateway-flag to fallback_payments_test or vice versa to reflect the example above and to keep it consistent.
There was a problem hiding this comment.
Great point--thanks!
|
|
||
| 1. Enable the [LaunchDarkly integration][1] in Datadog. | ||
| 1. Go to **Flags > `<your-feature-flag-name>` > Settings** in LaunchDarkly. | ||
| 1. In **Custom properties**, add a tag with key `service` and value `<your-service-name>`, matching your Datadog service name exactly. |
There was a problem hiding this comment.
Maybe we should be explicit that in the following example, the Datadog service (DD_SERVICE) is payments_api And after submitting the event, users can navigate to the payments_api service catalog page and be able to see the fallback_payments_test feature flag in the change tracking widget.
What does this PR do? What is the motivation?
Adds a dedicated page for feature flag tracking with Change Tracking.
Consolidates/removes existing feature flag tracking info on the Change Tracking landing page.
TODO: Update Launchdarkly page in integrations-extras (separate PR)
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes