-
Notifications
You must be signed in to change notification settings - Fork 95
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
Derive stream name from fluentd tag #67
Labels
Milestone
Comments
cbroglie
pushed a commit
to cbroglie/aws-fluent-plugin-kinesis
that referenced
this issue
May 14, 2016
Add support for kinesis_producer to derive the stream name by concatenating stream_name_prefix (new configuration option) and the fluentd tag. Fixes awslabs#67.
This was referenced May 14, 2016
cbroglie
pushed a commit
to cbroglie/aws-fluent-plugin-kinesis
that referenced
this issue
May 17, 2016
Add support for kinesis_producer to derive the stream name by concatenating stream_name_prefix (new configuration option) and the fluentd tag. Fixes awslabs#67.
cbroglie
pushed a commit
to cbroglie/aws-fluent-plugin-kinesis
that referenced
this issue
May 19, 2016
Add support for kinesis_producer to derive the stream name by concatenating stream_name_prefix (new configuration option) and the fluentd tag. Fixes awslabs#67.
Hi @cbroglie , I've released v1.1.0 and it contains this contribution. Thank you for your PR! |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have an application where we would like to route data to different Kinesis streams based on the fluentd tag. This is doable by specifying a different
<match></match>
configuration for each tag, but it means that there will be a separate KPL process for each configuration. And if we have 20 different streams, that means 20 instances of the KPL process, which wastes resources.Since the KPL requires the stream name to be specified with each record, the fluentd plugin can dynamically determine the stream name for each record it processes. One possible way to do this would be to allow users to specify a stream name prefix, and a regex to extract other data from the tag. A simpler (and more efficient) alternative would be a simple concatenation.
I'm happy to provide a PR for this functionality, if there is interest in accepting it.
The text was updated successfully, but these errors were encountered: