Ddjessicay/otel fleet page #32910
Ddjessicay/otel fleet page #32910
Conversation
Ddjessicay/otel ddot page
Ddjessicay/otel oss page
brett0000FF
left a comment
brett0000FF
left a comment
There was a problem hiding this comment.
Thanks for this! Just left a few comments and suggestions.
| - Send a flare from within your organization, reducing the time it takes to debug issues on an Agent. | ||
| - View the latest Agent and OTel Collector configurations along with historical changes to help confirm deployment updates and ensure configuration consistency. | ||
| - Ensure your fleet of Agents and OTel Collectors are using the latest feature enhancements by identifying and upgrading outdated versions. | ||
| - Send a flare from within your organization, reducing the time it takes to debug issues on an Agent or DDOT Collector. |
There was a problem hiding this comment.
Can users actually trigger a remote flare for a standalone OTel Collector via the UI? In the Send a remote flare section, it only mentions Agents.
There was a problem hiding this comment.
yes so it's a bit nuanced because flare capability is currently only available for agent / ddot, not yet for upstream oss collectors. Would appreciate your help articulating this here and in the flare section
There was a problem hiding this comment.
Noted! Added an alert box suggestion to that section: https://github.com/DataDog/documentation/pull/32910/files#r2543889208.
Co-authored-by: Brett Blue <[email protected]>
Co-authored-by: Brett Blue <[email protected]>
|
|
||
| ### Send a remote flare | ||
|
|
||
| After you enable Remote Configuration on an Agent, you can send a flare from Datadog. For instructions on sending a flare, see [Send a flare from the Datadog site][7]. |
There was a problem hiding this comment.
| You can send a flare from the Datadog Agent or DDOT Collector after enabling Remote Configuration on the Agent. For instructions on sending a flare, see [Send a flare from the Datadog site][7]. |
There was a problem hiding this comment.
Can we change the copy to "You can send a flare from the Datadog Agent or DDOT after enabling Remote Configuration on the Agent. For instructions..." and remove the alert?
Trying to only call out unsupported features when necessary
| - Send a flare from within your organization, reducing the time it takes to debug issues on an Agent. | ||
| - View the latest Agent and OTel Collector configurations along with historical changes to help confirm deployment updates and ensure configuration consistency. | ||
| - Ensure your fleet of Agents and OTel Collectors are using the latest feature enhancements by identifying and upgrading outdated versions. | ||
| - Send a flare from within your organization, reducing the time it takes to debug issues on an Agent or DDOT Collector. |
There was a problem hiding this comment.
Noted! Added an alert box suggestion to that section: https://github.com/DataDog/documentation/pull/32910/files#r2543889208.
2 participants
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.
Additional notes