-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Cherry-pick #22793 to 7.x: [Ingest Management] Agent expose metrics #23105
Conversation
* [Ingest Manager] Log level reloadable from fleet (elastic#22690) [Ingest Manager] Log level reloadable from fleet (elastic#22690) * aa * create drop * updated drop * process contains everything * drop start time * undo exposed endpoint * sanitize dataset name * ups * agent expose http * collect all metrics from beats * colelct all from beats * golint * cleaner docs * updated structure * cgroup * long live file saving issues (cherry picked from commit 49c8d87)
Pinging @elastic/ingest-management (Team:Ingest Management) |
This PR contains #23106 for the changelog. |
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change lgtm, but the tests failed?
@v1v Have you ever see that?
|
Yep, that's related to the cloud testing that was enabled by default, so it seems there is a bottleneck in the number of resources. @jsoriano pointed that the cloud testing was on demand rather by default, but when moving to the monorepo jenkinsfile.yml approach I enabled the cloud testing by default, not sure what's the best strategy here |
Maybe we should disable them?
This is worrying, could it be that db instances are not being properly destroyed? |
Cherry-pick of PR #22793 to 7.x branch. Original message:
What does this PR do?
Using system package focused on agent process we are collecting CPU,disk and memory metrics which are sent to ds.elastic_agent-elastic-agent
At first i was playing with exposing endpoint and using
beat
module to collect some information about agent but i let it go as most of information collected using this module is not relevant expect for go-routines and it makes code bloated with unnecessary setups providing empty values for fields which are noncollectable/unreportable from agent point of view.Why is it important?
#22394
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Example of final doc
linux
mac