-
Notifications
You must be signed in to change notification settings - Fork 57
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
kinesis_stream_name as token for config reference #5
Comments
This should be possible using the new I'm sure there's a way to have this input plugin add these config values as metadata fields, so that they can be referenced by config but don't pollute the output. |
@codekitchen - that would be great! Do you know if you can reference those fields in outputs too, specifically it he elasticsearch index config? example:
|
I think that would work with syntax |
@nickmaccarthy thinking about this some more, it seems like something that should probably be implemented in logstash itself, rather than in this plugin, so that all plugins get this enhancement. Would you mind moving this feature request over to https://github.com/elastic/logstash/issues ? |
As a similar request, it would be great if application_name can be referenced. Kinesis stream names may contain upper case letters (not allowed as ES index name) and sometimes not customizable. |
I'm not sure if this ever got filed against logstash core. I still think it makes the most sense to implement this there, it'd be silly for every plugin to implement it individually. |
Dont know if its possible or not, but it would be nice have the
kinesis_stream_name
as a token we can reference in the rest of the logstash config. In my particular case, it would allow us to more easily specify which elasticsearch index this stream data should go to.For example, assuming we are pulling from our stream name
foobar
we could add this in our logstash config to ensure it goes to the right index in elasticsearch:In fact, it would be great if all of the input config options could be referenced.
The text was updated successfully, but these errors were encountered: