-
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
[Agent] Expose stream.* data in every event #17468
[Agent] Expose stream.* data in every event #17468
Conversation
Pinging @elastic/ingest-management (Project:fleet) |
@hbharding It is an error that you are assigned to this PR? |
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.
Small comment concerning the document block of a function otherwise, LGTM Good workd @michalpristas
@@ -429,6 +436,117 @@ func InjectIndex(indexType string) *InjectIndexRule { | |||
} | |||
} | |||
|
|||
// InjectStreamProcessorRule expect target to be a collection of fields including | |||
// _meta_index map with dataset, index and namespace keys defined. |
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.
I think this comment need to be changed since we do not have the _meta_index
present in the code?
[Agent] Expose stream.* data in every event (elastic#17468) (cherry picked from commit 70fba87)
What does this PR do?
This PR generates a processor for each input exposing stream.[namespace/type/dataset] values to each event.
Why is it important?
Some modules define like Suricata a single input where mixed events are generated: metrics, logs or alerts. The identification of the data is often done in the ingest pipeline, where the type is generated from fields or values from the data.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Fixes: #16562