-
Notifications
You must be signed in to change notification settings - Fork 1.2k
DOCS-12323: Bits AI Kubernetes Remediation #32858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
cswatt
wants to merge
4
commits into
master
Choose a base branch
from
cswatt/k8s-remediation
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| --- | ||
| title: Bits AI Kubernetes Remediation | ||
| description: Discover and automatically remediate Kubernetes errors with Bits AI Kubernetes Remediation | ||
| further_reading: | ||
| - link: 'https://www.datadoghq.com/blog/kubernetes-active-remediation-ai/' | ||
| tag: 'blog' | ||
| text: 'Accelerate Kubernetes issue resolution with AI-powered guided remediation' | ||
| --- | ||
|
|
||
| Bits AI Kubernetes Remediation analyzes and fixes Kubernetes errors in your infrastructure. | ||
|
|
||
| The following Kubernetes errors are supported: | ||
| - `CrashLoopBackOff` | ||
| - `ErrImagePull` | ||
| - `ImagePullBackOff` | ||
| - `OOMKilled` | ||
| - `CreateContainerError` | ||
| - `CreateContainerConfigError` | ||
|
|
||
| ## Usage | ||
|
|
||
| You can launch Bits AI Kubernetes Remediation from multiple locations within Datadog: | ||
| - **From a Kubernetes monitor**: In the _Troubleshooting_ section, select a workload under _Problematic Workloads_. | ||
| - **From [Kubernetes Explorer][2]**: Hover over an error to see more information about the alert and the affected workload(s), and click _Start Remediation_. | ||
| - **From the [Kubernetes Remediation][1] tab**: Select a workload from the list. | ||
|
|
||
| Any one of these actions opens a Remediation side panel that displays: | ||
|
|
||
| - An AI-powered explanation for root cause, based on collected telemetry and known patterns | ||
| - Recommended next steps, which you may be able to [perform directly from Datadog](#remediate-from-datadog) | ||
| - Related information, including recent deployments, error logs, Kubernetes events, etc. | ||
|
|
||
| {{< img src="containers/remediation/side_panel2.png" alt="Remediation side panel opened for a workload with a CrashLoopBackOff error. Displays a What Happened section with a Bits AI-powered explanation of the error's root cause. Below, a Recommended Next Steps section where the user can inspect the workload manifest. Step-by-step instructions for a suggested fix are also displayed." style="width:80%;" >}} | ||
|
|
||
| ### Remediate from Datadog | ||
|
|
||
| If your repositories are [connected to Datadog][4], and an error can be fixed by changing code in one of these connected repositories, then you can use Bits AI to perform the remediation action directly from Datadog. For other problem scenarios, Bits AI provides a detailed list of remediation steps to follow. | ||
|
|
||
| {{% collapse-content title="Example: Increasing memory limit for a deployment" level="h4" expanded=true id="example-pr" %}} | ||
|
|
||
| {{< img src="containers/remediation/bitsai_action2.mp4" alt="In a Remediation side panel, the Recommended Next Steps section suggests that the user 'Increase memory limit'. The user enters a new value for the memory limit, increasing it from 10 mebibytes to 20 mebibytes. Clicking Fix with Bits AI brings up a dialog that prompts the user to select a connected repository. " video="true" style="width:80%;" >}} | ||
|
|
||
| When a pod is terminated because the memory usage exceeded its limit, you may be able to fix the error by increasing your container's memory limit. | ||
|
|
||
| 1. Click **Edit Memory Limit**. | ||
| 2. Adjust your limit so that it is higher than what your container normally uses. | ||
| 3. Click **Fix with Bits AI**. | ||
| 4. On the next page, select the repository where your deployment is defined, and review the proposed changes. Click **Fix with Bits** to create a pull request. | ||
| 5. You are redirected to a Bits [Code Session][3], where you can verify that the Bits AI Dev Agent identified the specific configuration file where your memory limits are defined. Click **View Pull Request** to view the pull request in GitHub. | ||
| {{% /collapse-content %}} | ||
|
|
||
| ## Further reading | ||
|
|
||
| {{< partial name="whats-next/whats-next.html" >}} | ||
|
|
||
| [1]: https://app.datadoghq.com/orchestration/remediation | ||
| [2]: https://app.datadoghq.com/orchestration/explorer/pod | ||
| [3]: https://app.datadoghq.com/code?tab=my-sessions | ||
| [4]: https://docs.datadoghq.com/integrations/guide/source-code-integration/?tab=githubsaasonprem#connect-your-git-repositories-to-datadog | ||
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i know these are alphabetical, but i would lead with the below 4 issue types if possible as they're the most common