Skip to content

[9.0](backport #45251) Update user agent #45493

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

Open
wants to merge 2 commits into
base: 9.0
Choose a base branch
from
Open

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 21, 2025

Proposed commit message

Update default user agent to distinguish between all beat modes:

  • Standalone indicates that the beat is not running under agent.
  • Unmanaged indicates that the beat is running under agent but not managed by Fleet.
  • Managed indicates that the beat is running under agent and managed by Fleet.

privilege mode information is only exposed under agent

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Users relying on specific user agents could be impacted. We've made no guarantees of stability for those and the only parts that changes are in the comments section.

Author's Checklist

  • verify user agent from a standalone agent
  • verify user agent from an unmanaged agent
  • verify user agent from a managed agent

This is an automatic backport of pull request #45251 done by [Mergify](https://mergify.com).

distinguish between all beat modes:

* Standalone indicates that the beat is not running under agent.
* Unmanaged indicates that the beat is running under agent but not managed by Fleet.
* Managed indicates that the beat is running under agent and managed by Fleet.

privilege mode information is only exposed under agent

(cherry picked from commit 2a99bfa)

# Conflicts:
#	NOTICE.txt
#	go.mod
#	go.sum
@mergify mergify bot requested review from a team as code owners July 21, 2025 22:07
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jul 21, 2025
@mergify mergify bot requested review from andrzej-stencel and VihasMakwana and removed request for a team July 21, 2025 22:07
Copy link
Contributor Author

mergify bot commented Jul 21, 2025

Cherry-pick of 2a99bfa has failed:

On branch mergify/bp/9.0/pr-45251
Your branch is up to date with 'origin/9.0'.

You are currently cherry-picking commit 2a99bfaa5.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG.next.asciidoc
	modified:   libbeat/beat/beat.go
	modified:   libbeat/beat/beat_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 21, 2025
@mergify mergify bot mentioned this pull request Jul 21, 2025
7 tasks
@github-actions github-actions bot added enhancement Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Jul 21, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request enhancement Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants