[pull] master from DataDog:master

config/_default/menus/api.en.yaml

@@ -11743,6 +11743,42 @@ menu:
       url: /api/latest/feature-flags/
       identifier: feature-flags
       generated: true
+    - name: Update a variant
+      url: /api/latest/feature-flags/update-a-variant/
+      identifier: feature-flags-update-a-variant
+      parent: feature-flags
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - UpdateVariantForFeatureFlag
+        unstable: []
+        order: 21
+    - name: Delete a variant
+      url: /api/latest/feature-flags/delete-a-variant/
+      identifier: feature-flags-delete-a-variant
+      parent: feature-flags
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - DeleteVariantFromFeatureFlag
+        unstable: []
+        order: 20
+    - name: Add a variant to a feature flag
+      url: /api/latest/feature-flags/add-a-variant-to-a-feature-flag/
+      identifier: feature-flags-add-a-variant-to-a-feature-flag
+      parent: feature-flags
+      generated: true
+      params:
+        versions:
+          - v2
+        operationids:
+          - CreateVariantForFeatureFlag
+        unstable: []
+        order: 22
     - name: Unarchive a feature flag
       url: /api/latest/feature-flags/unarchive-a-feature-flag/
       identifier: feature-flags-unarchive-a-feature-flag

content/en/api/latest/feature-flags/add-a-variant-to-a-feature-flag/index.md

@@ -0,0 +1,3 @@
+---
+title: Add a variant to a feature flag
+---

content/en/api/latest/feature-flags/delete-a-variant/index.md

@@ -0,0 +1,3 @@
+---
+title: Delete a variant
+---

content/en/api/latest/feature-flags/update-a-variant/index.md

@@ -0,0 +1,3 @@
+---
+title: Update a variant
+---

content/en/continuous_integration/pipelines/automatic_retries.md

@@ -36,6 +36,7 @@ When a job in your CI pipeline fails:
 
 To use automatic job retries:
 - CI Visibility must be enabled for your [GitHub Actions][1] or [GitLab][2] integration.
+- For GitHub Actions, the [Datadog GitHub App][8] must have the **Actions: Write** permission.
 - The [Datadog Source Code Integration][3] must be configured for the repositories where you'd like to use automatic retries.
 - Datadog must have indexed CI job logs for the repositories where you'd like to use automatic retries (see [Collect job logs for GitHub Actions][4] or [Collect job logs for GitLab][5]).
 - To enable this feature, you must have the **CI Provider Settings Write** permission in Datadog.
@@ -100,3 +101,4 @@ A failed job is not retried when:
 [5]: /continuous_integration/pipelines/gitlab/#collect-job-logs
 [6]: /continuous_integration/guides/use_ci_jobs_failure_analysis/
 [7]: https://app.datadoghq.com/ci/settings/ci-cd/repositories
+[8]: /continuous_integration/pipelines/github/#configure-a-github-app

content/en/incident_response/on-call/_index.md

@@ -22,7 +22,7 @@ cascade:
 
 Datadog On-Call integrates monitoring, paging, and incident response into one platform.
 
-{{< img src="service_management/oncall/oncall_overview.png" alt="Overview of how Pages are routed. From a monitor, incident, security signal, or API call, the Page is sent to a Team (e.g. 'payments-team'), then to routing rules (e.g. based on priority) then to an escalation policy. There, it can be sent to a schedule or directly to a user." style="width:100%;" >}}
+{{< img src="incident_response/on-call/oncall_overview.png" alt="Overview of how Pages are routed. From a monitor, incident, security signal, or API call, the Page is sent to a Team (e.g. 'payments-team'), then to routing rules (e.g. based on priority) then to an escalation policy. There, it can be sent to a schedule or directly to a user." style="width:100%;" >}}
 
 ## Concepts
 
@@ -36,15 +36,15 @@ Datadog On-Call integrates monitoring, paging, and incident response into one pl
 
 **Teams** are the central organizational unit of Datadog On-Call. When a notification is triggered in Datadog, a **Page** is sent to the designated On-Call Team.
 
-{{< img src="service_management/oncall/notification_page.png" alt="Notification that mentions an On-Call Team." style="width:80%;" >}}
+{{< img src="incident_response/on-call/notification_page.png" alt="Notification that mentions an On-Call Team." style="width:80%;" >}}
 
 Each Team owns **escalation policies** and **schedules**. Escalation policies define how a Page is sent to various schedules, such as _Checkout Operations - Interrupt Handler_, _Primary_, and _Secondary_ in the following screenshot. Each Team can also configure **routing rules** to route Pages to different escalation policies.
 
-{{< img src="service_management/oncall/escalation_policy.png" alt="A sample escalation policy." style="width:80%;" >}}
+{{< img src="incident_response/on-call/escalation_policy.png" alt="A sample escalation policy." style="width:80%;" >}}
 
 A schedule defines specific times when Team members are assigned to respond to Pages. Schedules organize and manage the availability of Team members across different time zones and shifts.
 
-{{< img src="service_management/oncall/schedule.png" alt="A sample schedule, with multiple layers for JP, EU, and US business hours." style="width:80%;" >}}
+{{< img src="incident_response/on-call/schedule.png" alt="A sample schedule, with multiple layers for JP, EU, and US business hours." style="width:80%;" >}}
 
 ## Granular access control
 

content/en/incident_response/on-call/automations.md

@@ -22,7 +22,7 @@ further_reading:
 
 ## Overview
 
-{{< img src="service_management/oncall/handover-automation.png" alt="The Handover Automation section on an On-Call team page" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation.png" alt="The Handover Automation section on an On-Call team page" style="width:80%;" >}}
 
 Handover automations run automatically when on-call duty passes from one person to another. They handle tasks that teams typically manage with custom scripts, such as notifying other systems about who's on-call, updating internal chat channels, or triggering downstream workflows.
 
@@ -73,27 +73,27 @@ For example, you can use this action to:
 
 Posts a handover summary to a Slack channel showing who is handing off to whom for each selected schedule. You can also include an AI-generated shift summary.
 
-{{< img src="service_management/oncall/handover-automation-slack-message.png" alt="Example Slack handover message showing shift change details" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-slack-message.png" alt="Example Slack handover message showing shift change details" style="width:80%;" >}}
 
 #### Update channel topic
 
 Updates a Slack channel topic when a shift changes. Use numbered variables (`{{1}}`, `{{2}}`, and so on) in a customizable template to reference responders in schedule order. For example, `On-call: {{1}} (backup: {{2}})` resolves to the primary and secondary on-call responders when the shift changes.
 
-{{< img src="service_management/oncall/handover-automation-slack-channel-topic.png" alt="Configuration form for the Slack Update channel topic automation" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-slack-channel-topic.png" alt="Configuration form for the Slack Update channel topic automation" style="width:80%;" >}}
 
 Channel topics have a character limit. The UI validates the template before saving.
 
 #### Send a direct message
 
 Sends a direct message to the incoming on-call responder when their shift begins.
 
-{{< img src="service_management/oncall/handover-automation-slack-direct-message.png" alt="Configuration form for the Slack Send a direct message automation" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-slack-direct-message.png" alt="Configuration form for the Slack Send a direct message automation" style="width:80%;" >}}
 
 #### Update user group
 
 Updates the members of a Slack user group to match the current on-call responders for the selected schedules.
 
-{{< img src="service_management/oncall/handover-automation-slack-update-group.png" alt="Configuration form for the Slack Update user group automation" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-slack-update-group.png" alt="Configuration form for the Slack Update user group automation" style="width:80%;" >}}
 
 **Note**: This action requires `usergroups:read` and `usergroups:write` permissions on the Datadog Slack app. If these permissions are missing, the UI displays a warning with a link to enable them.
 
@@ -103,19 +103,19 @@ Updates the members of a Slack user group to match the current on-call responder
 
 Posts a handover summary to a Microsoft Teams channel showing who is handing off to whom for each selected schedule. You can also include an AI-generated shift summary.
 
-{{< img src="service_management/oncall/handover-automation-ms-teams-message.png" alt="Configuration form for the Microsoft Teams Send message automation" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-ms-teams-message.png" alt="Configuration form for the Microsoft Teams Send message automation" style="width:80%;" >}}
 
 #### Update channel description
 
 Updates a Microsoft Teams channel description when a shift changes. Use numbered variables (`{{1}}`, `{{2}}`, and so on) in a customizable template to reference responders in schedule order. For example, `On-call: {{1}} (backup: {{2}})` resolves to the primary and secondary on-call responders when the shift changes.
 
-{{< img src="service_management/oncall/handover-automation-ms-teams-channel-topic.png" alt="Configuration form for the Microsoft Teams Update channel description automation" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-ms-teams-channel-topic.png" alt="Configuration form for the Microsoft Teams Update channel description automation" style="width:80%;" >}}
 
 #### Send a direct message
 
 Sends a direct message to the incoming on-call responder when their shift begins.
 
-{{< img src="service_management/oncall/handover-automation-ms-teams-direct-message.png" alt="Configuration form for the Microsoft Teams Send a direct message automation" style="width:80%;" >}}
+{{< img src="incident_response/on-call/automations/handover-automation-ms-teams-direct-message.png" alt="Configuration form for the Microsoft Teams Send a direct message automation" style="width:80%;" >}}
 
 ## Troubleshooting
 

content/en/incident_response/on-call/escalation_policies.md

@@ -13,7 +13,7 @@ In Datadog On-Call, escalation policies ensure that Pages are promptly addressed
 Datadog creates a default escalation policy when you [onboard a Team to On-Call][1].
 
 ## Create a new escalation policy
-{{< img src="service_management/oncall/escalation_policy_2.png" alt="A sample escalation policy." style="width:100%;" >}}
+{{< img src="incident_response/on-call/escalation_policies/escalation_policy_2.png" alt="A sample escalation policy." style="width:100%;" >}}
 
 1. Go to [**On-Call** > **Escalation Policies**][2].
 1. Select [**+ New Escalation Policy**][3].
@@ -24,13 +24,13 @@ Datadog creates a default escalation policy when you [onboard a Team to On-Call]
 	   1. Select one of the following notification methods: `Notify All`, `Round Robin`. See [Escalation policy notification types](#escalation-policy-step-notification-types) for details.
 	   1. Specify how many minutes the recipient has to acknowledge the Page before it is escalated to the next tier.
    For example, the following will notify the current on-call user when a Page is triggered. It will escalate to Jane Doe if John does not acknowledge the Page within 5 minutes.
-   {{< img src="service_management/oncall/escalation_policy_2_steps_v2.png" alt="An escalation policy configured to notify the scheduled on-call user and escalate to Jane Doe if the Page is not acknowledged after 5 minutes." style="width:100%;" >}}
+   {{< img src="incident_response/on-call/escalation_policies/escalation_policy_2_steps_v2.png" alt="An escalation policy configured to notify the scheduled on-call user and escalate to Jane Doe if the Page is not acknowledged after 5 minutes." style="width:100%;" >}}
 1. Set how many times to repeat the steps if no one acknowledges the Page.
 1. Select whether Datadog should automatically update the Page status to **Resolved** after executing all rules and repeats.
 
 ## Escalation policy step notification types
 In each step of an escalation policy, you can keep the standard `Notify All` behavior or opt-in for `Round Robin`.
-{{< img src="service_management/oncall/escalation_policy_notification_type.png" alt="Notification type selector in Escalation Policy creation" style="width:100%;" >}}
+{{< img src="incident_response/on-call/escalation_policies/escalation_policy_notification_type.png" alt="Notification type selector in Escalation Policy creation" style="width:100%;" >}}
 
 ### Notify all (default)
 Notify all targets of the step at the same time.
@@ -58,7 +58,7 @@ If you want the Page to go to the next target in the round robin, use only one r
 In each step of an escalation policy, you can notify individual users, entire teams, or whoever is on-call in a schedule.
 
 ### Schedules
-{{< img src="service_management/oncall/escalation_policy_notify_schedule.png" alt="A sample escalation policy step that notifies a schedule." style="width:100%;" >}}
+{{< img src="incident_response/on-call/escalation_policies/escalation_policy_notify_schedule.png" alt="A sample escalation policy step that notifies a schedule." style="width:100%;" >}}
 
 Escalation policies can notify whoever is on-call according to a predefined schedule. The system checks the schedule and notifies the person or group that is actively on-call during the incident. Using schedules is beneficial for:
 
@@ -68,10 +68,10 @@ Escalation policies can notify whoever is on-call according to a predefined sche
 
 If no one is on-call for a given schedule, the escalation step gracefully skips and the process moves forward without delays or interruptions. The UI indicates a skipped escalation.
 
-{{< img src="service_management/oncall/escalation_policy_schedule_skipped.png" alt="A sample escalation policy indicating a skipped escalation due to no one being on-call." style="width:100%;" >}}
+{{< img src="incident_response/on-call/escalation_policies/escalation_policy_schedule_skipped.png" alt="A sample escalation policy indicating a skipped escalation due to no one being on-call." style="width:100%;" >}}
 
 ### Users
-{{< img src="service_management/oncall/escalation_policy_notify_user.png" alt="A sample escalation policy that specifies a user in the escalation policy." style="width:100%;" >}}
+{{< img src="incident_response/on-call/escalation_policies/escalation_policy_notify_user.png" alt="A sample escalation policy that specifies a user in the escalation policy." style="width:100%;" >}}
 
 You can include specific users in an escalation policy to ensure key individuals are always notified in the event of a Page. Common use cases for directly paging a user are:
 
@@ -80,7 +80,7 @@ You can include specific users in an escalation policy to ensure key individuals
 - Routing alerts to a backup responder if the primary contact is unavailable.
 
 ### Teams
-{{< img src="service_management/oncall/escalation_policy_notify_team.png" alt="A sample escalation policy that notifies an entire Team." style="width:100%;" >}}
+{{< img src="incident_response/on-call/escalation_policies/escalation_policy_notify_team.png" alt="A sample escalation policy that notifies an entire Team." style="width:100%;" >}}
 
 Common use cases for paging an entire Team are:
 

content/en/incident_response/on-call/guides/migrate-your-opsgenie-resources-to-on-call.md

@@ -49,7 +49,7 @@ The migration follows a six-step wizard-style process in Datadog. Complete all s
 1. If you have multiple regions configured, select your OpsGenie account's region from the dropdown. 
 1. Datadog loads all your OpsGenie teams in a searchable, paginated list. Select the team to migrate, then select **Next**. A preview pane shows the team's members and settings.
 
-{{< img src="service_management/oncall/import-opsgenie-team-2.png" alt="OpsGenie team list with a preview pane showing the selected team's members and settings" style="width:95%;" >}}
+{{< img src="incident_response/on-call/guides/migrate-your-opsgenie-resources-to-on-call/import-opsgenie-team-2.png" alt="OpsGenie team list with a preview pane showing the selected team's members and settings" style="width:95%;" >}}
 
 **Note**: If a team was previously imported, Datadog indicates this.
 
@@ -61,7 +61,7 @@ The migration follows a six-step wizard-style process in Datadog. Complete all s
    - Map to a different Datadog team that you select.
    - Create a new team. Enter a team name to create a Datadog team based on the structure and members of the OpsGenie team.
 
-   {{< img src="service_management/oncall/map-opsgenie-team-to-datadog-team-2.png" alt="Mapping options for assigning an OpsGenie team to an existing or new Datadog team" style="width:95%;" >}}
+   {{< img src="incident_response/on-call/guides/migrate-your-opsgenie-resources-to-on-call/map-opsgenie-team-to-datadog-team-2.png" alt="Mapping options for assigning an OpsGenie team to an existing or new Datadog team" style="width:95%;" >}}
 
 1. When the mapping is correct, select **Next**.
 
@@ -70,7 +70,7 @@ The migration follows a six-step wizard-style process in Datadog. Complete all s
 1. Browse your OpsGenie escalation policies. You can filter policies by team.
 1. Select an escalation policy to import. The wizard displays the full policy details, including rules, recipients, and schedules.
 
-{{< img src="service_management/oncall/import-opsgenie-escalation-policy.png" alt="OpsGenie escalation policy list with policy details shown for the selected policy" style="width:95%;" >}}
+{{< img src="incident_response/on-call/guides/migrate-your-opsgenie-resources-to-on-call/import-opsgenie-escalation-policy.png" alt="OpsGenie escalation policy list with policy details shown for the selected policy" style="width:95%;" >}}
 
 ### Step 4: Map users