Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Render Mustache expressions in routing rules datasets values #1393
Render Mustache expressions in routing rules datasets values #1393
Changes from 6 commits
681e688
b191cd0
91cf7de
cfea2c4
4a678ae
edd774a
9b9136c
5c251cf
ac18517
4db10c6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
For a test this looks enough, but isn't this intended to be used with fields that contain datasets? Like
{{data_stream.dataset}}
or similar?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.
In general, expressions in the routing rules enable the rule to pick a dataset or namespace value for a field in the log event.
For example, the Kubernetes integration picks the dataset value from the
{{kubernetes.labels.elastic_co/dataset}}
field.Unfortunately, the Firehose event does not offer a lot of fields with values compatible with the data stream naming restrictions.
So, I imagined a scenario where users want to partition the log events into multiple AWS account-based data streams using
{{cloud.account.id}}
. But it's a bit confusing.The other option is to add an extra field in the log event, for example,
{{labels.elastic_co/dataset}}
, and use this field in the rule. It does not exist in the Firehose realm but is less confusing overall. WDYT?