Update take_action.md#36562
Conversation
updating to match newly GAed features
akarpz
left a comment
akarpz
left a comment
There was a problem hiding this comment.
A few editorial notes — mostly grammar and Vale style. Inline suggestions below.
| Triage Suggestions help you coordinate the response without leaving the investigation page. Bits uses investigation context to prefill messages, incident descriptions, or ticket metadata, so you can take common response tasks with a single click. | ||
|
|
||
| Suggestions include but are not limited to | ||
| - Sending Slack messages to update your team on the investigation results |
There was a problem hiding this comment.
The previous version of this list also included Microsoft Teams messages, PagerDuty incidents, and Datadog Case Management cases. Was dropping those intentional? If they're still supported, the shorter list undersells what triage suggestions can do.
git-thuerk-done
left a comment
git-thuerk-done
left a comment
There was a problem hiding this comment.
Good restructure — the three-section layout with the upfront summary is clearer than the previous version. A few editorial items inline: missing colon, inconsistent product naming ("Bits" vs "Bits AI SRE"), temporal "will," and a couple of sentence-level fixes.
Also noting: the branch name akethini321-patch-2 doesn't follow the <name>/<description> convention, so no preview build will be generated.
|
|
||
| Bits AI SRE integrates with [Bits AI Dev Agent][2] to automatically generate code fixes. The Dev Agent connects to GitHub or GitLab to create production-ready pull requests and iterates on fixes using CI logs and developer feedback, and uses multiple Datadog products to generate contextual fixes. | ||
|
|
||
| To start receiving code fixes, [set up the Bits AI Dev Agent][1]. Then, if Bits AI SRE has determined a code-related root cause, you will automatically receive suggested code fixes. |
There was a problem hiding this comment.
Avoid temporal "will" — docs should be evergreen. Use present tense.
| To start receiving code fixes, [set up the Bits AI Dev Agent][1]. Then, if Bits AI SRE has determined a code-related root cause, you will automatically receive suggested code fixes. | |
| Bits AI SRE recommends corrective steps when applicable for the root cause. These recommendations can include commands that are fully configured, so you can copy them and run in your CLI. For example, Bits AI SRE may provide a `kubectl` command to restart or patch an affected Kubernetes deployment. |
|
|
||
| ## Run triage actions via chat | ||
| From chat, you can trigger triage actions without leaving the investigation workflow. | ||
| ## Remediation Recommendations |
There was a problem hiding this comment.
Missing blank line between the ## Triage Suggestions heading and the paragraph. The other headings on this page have a blank line — keep it consistent.
|
|
||
| After Bits AI SRE helps you identify a root cause, it can also help you take action as quickly as possible. | ||
| - Code Fixes help resolve code-related root causes. | ||
| - Remediation Recommendations provide corrective steps and fully configured commands. |
There was a problem hiding this comment.
This sentence chains three verbs ("connects," "iterates," "uses") and runs to 30 words. Consider splitting:
"The Dev Agent connects to GitHub or GitLab to create production-ready pull requests. It iterates on fixes using CI logs and developer feedback and uses multiple Datadog products to generate contextual fixes."
| - Code Fixes help resolve code-related root causes. | ||
| - Remediation Recommendations provide corrective steps and fully configured commands. | ||
| - Triage Suggestions help coordinate the response through connected tools. | ||
|
|
There was a problem hiding this comment.
Minor: "has determined" could be present tense for consistency with the rest of the page.
| To start receiving code fixes, [set up the Bits AI Dev Agent][1]. Then, if Bits AI SRE determines a code-related root cause, you automatically receive suggested code fixes. |
Co-authored-by: Adam Karpowich <[email protected]>
Co-authored-by: Adam Karpowich <[email protected]>
Co-authored-by: Adam Karpowich <[email protected]>
Co-authored-by: Adam Karpowich <[email protected]>
Co-authored-by: Adam Karpowich <[email protected]>
Co-authored-by: Alicia Thuerk <[email protected]>
Co-authored-by: Adam Karpowich <[email protected]>
Co-authored-by: Alicia Thuerk <[email protected]>
3 participants
updating to match newly GAed features
What does this PR do? What is the motivation?
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.
AI assistance
Additional notes