From bc37e8ac9054edf71ff80f1282144edb6a56f0f5 Mon Sep 17 00:00:00 2001 From: Anna Fenske Date: Thu, 21 May 2026 08:43:02 -0400 Subject: [PATCH] Add evaluation tracking, flag organization, and notifications docs Adds three Feature Flags concept pages and links getting started monitoring to evaluation tracking. Updates navigation menu entries. Co-authored-by: Cursor --- config/_default/menus/main.en.yaml | 19 +++++- .../concepts/evaluation_tracking.md | 35 +++++++++++ .../concepts/flag_organization.md | 34 +++++++++++ .../feature_flags/concepts/notifications.md | 60 +++++++++++++++++++ .../getting_started/feature_flags/_index.md | 5 +- 5 files changed, 148 insertions(+), 5 deletions(-) create mode 100644 content/en/feature_flags/concepts/evaluation_tracking.md create mode 100644 content/en/feature_flags/concepts/flag_organization.md create mode 100644 content/en/feature_flags/concepts/notifications.md diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 85a1d06ab61..30c4b1aeeb5 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -6077,16 +6077,31 @@ menu: parent: feature_flags_concepts identifier: feature_flags_concepts_distribution_channels weight: 305 + - name: Evaluation Tracking + url: feature_flags/concepts/evaluation_tracking + parent: feature_flags_concepts + identifier: feature_flags_concepts_evaluation_tracking + weight: 306 + - name: Flag Organization + url: feature_flags/concepts/flag_organization + parent: feature_flags_concepts + identifier: feature_flags_concepts_flag_organization + weight: 307 + - name: Notifications + url: feature_flags/concepts/notifications + parent: feature_flags_concepts + identifier: feature_flags_concepts_notifications + weight: 308 - name: Flag History url: feature_flags/concepts/flag_history parent: feature_flags_concepts identifier: feature_flags_history - weight: 306 + weight: 309 - name: MCP Server url: feature_flags/concepts/feature_flag_mcp_server parent: feature_flags_concepts identifier: feature_flags_mcp_server - weight: 307 + weight: 310 - name: .NET url: feature_flags/server/dotnet parent: feature_flags_server diff --git a/content/en/feature_flags/concepts/evaluation_tracking.md b/content/en/feature_flags/concepts/evaluation_tracking.md new file mode 100644 index 00000000000..94f75e1aa03 --- /dev/null +++ b/content/en/feature_flags/concepts/evaluation_tracking.md @@ -0,0 +1,35 @@ +--- +title: Evaluation Tracking +description: Monitor feature flag rollouts with evaluation metrics and real-time graphs in Datadog. +further_reading: +- link: "/feature_flags/concepts/targeting_rules" + tag: "Documentation" + text: "Targeting Rules and Filters" +- link: "/getting_started/feature_flags/" + tag: "Documentation" + text: "Getting Started with Feature Flags" +--- + +## Overview + +Evaluation tracking helps you monitor how feature flags are performing in production. Each time your application evaluates an enabled feature flag with an SDK, Datadog can capture evaluation metrics so you can see rollout progress and variant distribution. + +## Evaluations graph + +On the feature flag details page, the **Evaluations** graph shows how often your flag is evaluated over time. Use this graph to monitor the rollout of a feature flag—for example, to confirm traffic increases as you enable a flag or advance a progressive rollout. + +{{< img src="getting_started/feature_flags/real-time-flag-metrics.png" alt="Evaluations graph showing gradual ramp up in traffic" style="width:100%;" >}} + +## Evaluation metrics + +Evaluation metrics are captured each time you evaluate an enabled feature flag with an SDK. Metrics are broken down by **variant**, so you can see the actual distribution of traffic across variant values. + +When `DD_METRICS_OTEL_ENABLED=true` is set for server-side SDKs, each evaluation records a `feature_flag.evaluations` counter metric tagged with the flag key, result variant, and evaluation reason. See [Server-Side Feature Flags](/feature_flags/server/) for configuration details. + +## Targeting rule counts + +In the **Targeting Rules & Rollouts** section, you can see a count of subjects that have encountered each targeting rule or your default variant. Use these counts to validate that your filters and percentages match expected traffic patterns. + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} diff --git a/content/en/feature_flags/concepts/flag_organization.md b/content/en/feature_flags/concepts/flag_organization.md new file mode 100644 index 00000000000..bbc542df7a5 --- /dev/null +++ b/content/en/feature_flags/concepts/flag_organization.md @@ -0,0 +1,34 @@ +--- +title: Flag Organization +description: Organize and find feature flags with tags, team tags, and favorites. +further_reading: +- link: "/feature_flags/concepts/permissions" + tag: "Documentation" + text: "Permissions and Access Control" +--- + +## Overview + +As your organization adds more feature flags, organization tools help you find, filter, and prioritize the flags you work with most often. + +## Freeform tags + +**Tags** are freeform labels you can add to flags to organize them by project, team, feature area, or any dimension you choose. + +- Add tags when you create a flag or from the flag details page. +- Filter flags by tag on the Feature Flags search page. + +## Team tags + +**Team tags** associate flags with Datadog teams for ownership and accountability. + +- Filter flags by team on the search page. +- Toggle **My Teams** to view flags that belong to one or more teams you are a member of. + +## Favorites + +Favorite important flags in the UI to pin them to the top of your search results for quick access. + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} diff --git a/content/en/feature_flags/concepts/notifications.md b/content/en/feature_flags/concepts/notifications.md new file mode 100644 index 00000000000..945da901a6f --- /dev/null +++ b/content/en/feature_flags/concepts/notifications.md @@ -0,0 +1,60 @@ +--- +title: Notifications +description: Configure notification channels and alert types for Datadog Feature Flags. +further_reading: +- link: "/feature_flags/concepts/approvals" + tag: "Documentation" + text: "Approvals" +- link: "/integrations/slack/" + tag: "Documentation" + text: "Slack" +--- + +## Overview + +Feature Flags can send notifications when flag configuration changes or when rollouts require attention. Configure notification channels per flag to route alerts to the right team. + +## Set up notification platforms + +Before configuring flag notifications, set up the notification platform integration of your choice: + +- [Slack](/integrations/slack/) +- [Microsoft Teams](/integrations/microsoft-teams/) +- [PagerDuty](/integrations/pagerduty/) +- [Webhooks](/integrations/webhooks/) + +Email notifications are supported out of the box. + +## Configure notifications on a flag + +### New flag + +When you create a flag: + +1. Add a notification channel. +2. Select the notification types to send to that channel. + +Error-level notifications are always enabled so you receive urgent alerts—for example, when a canary rollout fails a guardrail check. + +### Existing flag + +1. Navigate to your flag's details page. +2. Open **Settings > Notifications**. +3. Configure the channel and notification types. + +## Notification types + +Feature Flags can send notifications for the following events: + +- Flag enabled or disabled in an environment +- Flag archived +- Progressive rollout started +- Targeting rule created, updated, or deleted +- Progressive rollout paused by a user +- Progressive rollout aborted by a user +- Progressive rollout paused by a guardrail +- Progressive rollout aborted by a guardrail + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} diff --git a/content/en/getting_started/feature_flags/_index.md b/content/en/getting_started/feature_flags/_index.md index dc7528274d0..0f08f5d939d 100644 --- a/content/en/getting_started/feature_flags/_index.md +++ b/content/en/getting_started/feature_flags/_index.md @@ -142,9 +142,7 @@ For percentage rollouts, see [Traffic Splitting and Randomization][8]. ### Step 5: Monitor your rollout -Monitor the feature rollout from the feature flag details page, which provides real-time exposure tracking and metrics such as **error rate** and **page load time**. As you incrementally release the feature with the flag, view the **Real-Time Metric Overview** panel in the Datadog UI to see how the feature impacts application performance. - -{{< img src="getting_started/feature_flags/real-time-flag-metrics.png" alt="Real-time flag metrics panel" style="width:100%;" >}} +Monitor rollout progress from the feature flag details page. See [Evaluation Tracking][9] for evaluations graphs, variant breakdowns, and targeting rule subject counts. ## Further reading @@ -158,3 +156,4 @@ Monitor the feature rollout from the feature flag details page, which provides r [6]: /feature_flags/concepts/distribution_channels/ [7]: /feature_flags/concepts/targeting_rules/ [8]: /feature_flags/concepts/traffic_splitting/ +[9]: /feature_flags/concepts/evaluation_tracking/