[AGENT] Schedule Agent Upgrades #33035
Open
+49
−13
Conversation
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
Contributor
Preview links (active after the
|
| ### Prerequisites | ||
| * **Disk space**: Datadog suggests at least 2GB for the initial Agent install and an additional 2GB for upgrading the Agent from Fleet Automation. Specifically, the upgrade requires 1.3GB in the `/opt/datadog-packages` directory on Linux, or `C:\ProgramData\Datadog\Installer\packages` on Windows. The extra space ensures that there is enough room to maintain two Agent installs temporarily during the upgrade process in case a rollback is needed. | ||
|
|
||
| ### Upgrade process |
Contributor
There was a problem hiding this comment.
Why did we bring upgrade process up?
|
|
||
| The Agent ensures that the appropriate permissions are set for these files. No configuration files are altered during the installation process. | ||
|
|
||
| ### How to upgrade Agents remotely |
Contributor
There was a problem hiding this comment.
We should float this higher
|
|
||
| Similar to a manual upgrade, expect a downtime of 5-30 seconds while the Agent restarts. The full upgrade process takes approximately 5 minutes. Around 2 minutes of this time is used for the upgrade process. The rest of the time is spent monitoring the upgrade to ensure stability and determining if a rollback is necessary. If the upgrade fails and a rollback is necessary, the Agent automatically reverts to the previously running Agent version. | ||
| To schedule your Agent upgrades: | ||
| 1. [Enable Remote Agent Management](#enable-remote-agent-management). |
Contributor
There was a problem hiding this comment.
Feels like we're repeating this step
| Windows: | ||
| * `C:\ProgramData\Datadog\Installer\packages` | ||
| * `C:\Program Files\Datadog\Datadog Agent` | ||
| 1. **Select the Agent version**. You have the option to upgrade the Agents to: |
Contributor
There was a problem hiding this comment.
Let's make simpler:
Select the target Agent version.
Contributor
There was a problem hiding this comment.
Let's make this more concise, rather than listing out the three options explicitly
Contributor
There was a problem hiding this comment.
Fine with not mentioning at all since screenshot mentions
| The Agent ensures that the appropriate permissions are set for these files. No configuration files are altered during the installation process. | ||
| {{< img src="/agent/fleet_automation/agent_upgrade_select_version1.png" alt="See a list of scheduled Agent upgrades." style="width:100%;" >}} | ||
|
|
||
| 1. **Specify the Agents to be upgraded**. You can use filtering or a search query to scope the Agents by various attributes including, the Agents' environment, operation system, or hostname. You can then see the Agents that are included within your specified scope along with those that are not eligible for deployment. Adjust your filter to include all the Agents you want to upgrade. |
Contributor
There was a problem hiding this comment.
Let's keep the scoping steps language consistent like the same example above:
Select the Agents you want to upgrade. You can target a group of Agents by filtering on host information or tags.
I think we're repeating this step though.
|
|
||
| {{< img src="/agent/fleet_automation/agent_upgrade_set_window.png" alt="Select the time frame for your Agent upgrades." style="width:100%;" >}} | ||
|
|
||
| 1. Optionally, click **+ Add Recipient** to set up notifications and receive updates on the deployment. You can notify individuals or communication integration channels like Slack, Teams, or PagerDuty. |
Contributor
There was a problem hiding this comment.
Let's remove "Optionally...Add Recipient" to"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do? What is the motivation?
This PR adds instructions for how to schedule your Agent upgrades.
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.
Additional notes