-
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
[Filebeat] Initial errors/failures observed when testing AbuseCH integration in Agentless #42815
Comments
This issue doesn't have a |
It looks like multiple goroutines are holding on to a configuration value.
|
I suspect this is from the ES state store seeing it and the top of the stack trace and also what it is doing in that stack trace: beats/libbeat/statestore/backend/es/store.go Lines 64 to 85 in 2200a16
CC @orestisfl The agent policy here has multiple CEL inputs running the same Filebeat process, so perhaps related to that. |
Hmm, can't see anything in the stack trace that is supposed to be writing to the configuration value for it to cause a concurrent map read and map write. However, if not all go routines are captured at the exact moment when the exception happens, the most likely candidate I see is goroutine 105:
This line here is just 4 lines above the current line:
and ApplyPreset() calls Merge() :
|
Please include configurations and logs if available.
elastic-agent-diagnostics-2025-02-20T20-36-47Z-00.zip
For confirmed bugs, please report:
Version:
9.0.0-beta1
Operating System:
Agentless Deployment
Steps to Reproduce:
ti_abusech
integration with agentless enabled usingelastic-package
to the instanceRunning it through the agent analyzer synposis looks like this:
and
The text was updated successfully, but these errors were encountered: