-
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
[fbreceiver] Default Processors are not being applied #42631
Comments
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
This is also happening for fbreceiver running as part of EDOT, in this test we add the processors manually otherwise the fields are not present. |
I looked a bit into this and it seems that the call that instantiate the processors is:
However it only applies the processors if beats/libbeat/publisher/processing/default.go Lines 118 to 124 in 090584e
This results in none of the |
I'm not entirely sure if this is a bug or just the default behavior. cc @leehinman |
When fbreceiver is created, it adds default processor to the settings here.
beats/x-pack/filebeat/fbreceiver/factory.go
Line 40 in 95b5dce
Expected:
It is expected that all documents ingested have
host
related fields added to it. According to this ref here https://www.elastic.co/guide/en/beats/filebeat/current/add-host-metadata.htmlGot:
Except for
host.name
, no other fields are part of the ingested doc.When we explicitly set the default processor in the config file. It correctly adds all
host
related fields.How to test this locally
cd x-pack/filebeat
mage docker:composeUp
filebeat-otel.yml
to following configCheck the document ingested
The text was updated successfully, but these errors were encountered: