-
Notifications
You must be signed in to change notification settings - Fork 5k
[8.19](backport #44438) [beat_receivers] move when monitoring is started #44470
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
Conversation
* [beat_receivers] move when monitoring is started (cherry picked from commit 82f47f7)
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
This pull request has not been merged yet. Could you please review and merge it @leehinman? 🙏 |
1 similar comment
|
This pull request has not been merged yet. Could you please review and merge it @leehinman? 🙏 |
|
@leehinman could you please resolve the conflicts? |
#43356 was not backported
|
This pull request is now in conflicts. Could you fix it? 🙏 |
fix merge conflicts
|
Closing because without #43356 being backported we won't have individual logging under multiple receivers. |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Proposed commit message
For beat receivers move when the HTTP endpoint is started to before when the
beateris created. This makes it likenormal" beats and will start the "stats" and "inputs" endpoints.
This does have duplication between mbreceiver and fbreceiver, we can refactor that back into
beatreceiverpackage when we refactor the location of thebeatreceiverpackage.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
None. Beats receivers not GA and this add "inputs" endpoint that was missing
Author's Checklist
How to test this PR locally
Filebeat
Metricbeat
Related issues
Use cases
Screenshots
Logs
This is an automatic backport of pull request #44438 done by [Mergify](https://mergify.com).