Skip to content

bits_remediation.md

Latest commit

 

History

History
84 lines (58 loc) · 4.69 KB

bits_remediation.md

File metadata and controls

84 lines (58 loc) · 4.69 KB
Raw
title Bits Remediation
description Learn how Bits provides actionable remediation next steps for root cause investigations.
aliases
/bits_ai/bits_ai_sre/remediate_issues/
/bits_ai/bits_investigation/remediate_issues/
/bits_ai/bits_ai_sre/take_action/
/bits_ai/bits_investigation/take_action/
site_support_id bits_remediation

{{< callout url="https://www.datadoghq.com/product-preview/bits-remediation/" >}} Bits Remediation includes capabilities in Preview. Click Request Access to join the Preview program. {{< /callout >}}

Automate code fixes

After Bits helps you identify a root cause from an investigation, it can also help you take action as quickly as possible.

Bits Investigation integrates with Bits Code to generate code fixes. Bits connects to your source code provider to create, update, and iterate on production-ready pull requests, based on existing issues detected by Datadog.

Code fixes are automatically generated by default for investigations with code-related root causes. To manually generate code fixes at your own discretion instead, disable automatic code fix generation in Settings.

  1. Set up Bits Code. After Bits determines a code-related root cause, a suggested code fix is generated in next steps by default.
  2. If automatic code fixes are disabled, manually generate a code fix from next steps.
  3. Chat with Bits within the code session to update the suggested code fix.
  4. Create a pull request for review and merge when ready.

{{< img src="bits_ai/bits_remediation/suggested_code_fix.png" alt="Bits Investigation hypothesis tree showing a root cause conclusion with a suggested code fix and other next steps" style="width:100%;" >}}

Run triage actions

From chat, you can trigger triage actions without leaving the investigation workflow.

Supported actions include:

  • Sending Slack and Microsoft Teams messages
  • Creating incidents in Datadog and PagerDuty
  • Paging engineers with Datadog On-Call
  • Creating cases in Datadog Case Management
  • Opening Jira tickets

Bits automatically pulls relevant context from the investigation and your connected integrations to prefill messages, incident descriptions, and ticket metadata. This reduces manual effort, helps ensure consistency, and accelerates response time.

Take action on your infrastructure

One-click actions are in Preview.

For infrastructure-related issues, Bits can recommend a remediation action, such as scaling a deployment, restarting a pod, or patching a resource.

  • Manual recommendations: Copy the suggested command (for example, a kubectl patch command) and run it in your own CLI.
  • One-click actions (Preview): Click Run to let Bits execute the suggested remediation action directly from the investigation context.

{{< img src="bits_ai/bits_remediation/one_click_action.png" alt="A suggested remediation action with instructions to restart a deployment, a Run button, and a Verify Resolution button" style="width:100%;" >}}

Kubernetes actions are supported in Preview, with more integration actions in progress. See the Action Catalog for the full list of supported actions and how to enable them in Datadog.

To run one-click Kubernetes actions, your organization needs:

  • A Private Action Runner with network access to your Kubernetes cluster, paired with a Connection to the Kubernetes integration.
  • A user role with permission to run actions and resolve the Kubernetes connection.

Govern how Bits takes remediation action

Bits Guardrails are in Preview.

Bits Guardrails let admins define which remediation actions Bits can take, where those actions apply, and who needs to approve them.

Guardrails require the Guardrails Read and Guardrails Write permissions. To create a guardrail:

  1. Choose the actions to target: Select one or more available actions for an integration (for example, Kubernetes) for the guardrail to target.
  2. Define guardrail scope: Specify the environment, service, and resource tags the guardrail applies to.
  3. Set the enforcement level: For the selected actions and scope, decide when Bits can take action.
    • Ask: Requires user approval before Bits executes actions. Choose which teams, roles, or individuals can approve.
    • Deny: Bits can recommend an action but cannot take it.

Validate that issues are resolved

Bits can verify whether a remediation action was applied successfully, and whether the original issue was resolved.