-
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
Stand-alone agent: it's not possible to get agent documents from elasticsearch #20992
Comments
Pinging @elastic/ingest-management (Team:Ingest Management) |
@michalpristas Can you take a look, it is a regression or the asserts is incorrect? |
it would be good to know the state of the Metricbeat / Filebeat processes at that point during the test, it seems likely they are not in proper working order. It is regression from prior success in the 7.9 and 8.0 branches that test stand-alone mode. I've run the test locally and see the failure. I'll poke into the containers now and report back |
This one broke it https://github.com/elastic/beats/pull/20839/files the thing is that this one creates a new logger which logs just one line and rotates the one used by main logger. main logger keeps logging into the one which one it thinks is the current one (logger does not see rotation) and therefore filebeat does not pick entries from (from its perspective) stale file (as it gets rotated) i will fix it next week (PTO tomorrow) or @blakerouse you can pick it up if you have some spare time |
I guess that @michalpristas Is that the issue? Do I need to instead pass the logger in? |
Meanwhile, we must be aware that the stand-alone tests will be broken until this gets fixed. @EricDavisX how can we effectively communicate this to the team? |
Email and slack chat of a quick message is all I can think of for now. Until we get tests in PR CI I think its just you and I that need to know. It does raise the question of communication and 'test skipping' type support as the project matures and we get it into CI that I'm sure will come up. |
@blakerouse i would suggest passing a logger, and create a named logger if needed |
Steps to Reproduce
Search Result:
Agent Log
where I can see only one error entry:
cc/ @EricDavisX
The text was updated successfully, but these errors were encountered: