Skip to content
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

Documentation on filebeat logstash-output is not clear for index setting #3558

Closed
JalehD opened this issue Feb 8, 2017 · 3 comments
Closed

Comments

@JalehD
Copy link

JalehD commented Feb 8, 2017

  • Version: any
  • Operating System: any

This documentation https://www.elastic.co/guide/en/beats/filebeat/5.2/logstash-output.html causes confusion in the role of the setting "index" , this might be a mistake in the doc due to differences of this setting between when it's used inlogstash-output versus when it's used in elasticsearch-output.

The document flow seems to also cause confusion as it starts with logstash configuration details.

@tsg
Copy link
Contributor

tsg commented Feb 13, 2017

The "index" option is passed to the Logstash metadata, and can be used in the LS elasticsearch output (that's the purpose of the LS configuration samples). The docs should definitely be clarified.

The document flow seems to also cause confusion as it starts with logstash configuration details.

Pinging @dedemorton for this one :)

@jakommo
Copy link
Contributor

jakommo commented Feb 13, 2017

I think we should also make it more clear that metadata fields are not part of the event at output time.
E.g. if you are doing something like Filebeat -> LS1 -> Redis -> LS2.
The meta data fields populated by Filebeat are only existent onLS1 and will not be passed to Redis, thus also missing in LS2 unless copied to a normal field via mutate or something in LS1.

andrewkroh pushed a commit that referenced this issue Mar 31, 2017
This resolves issue #3558 by clarifying how the contents of the @metadata field are used for setting the index. I've also done a little cleanup in general of the Logstash config docs.

As a little side project, I removed "Configuration" from the end of the topic titles for the reference content because the navigation is a lot easier to read (IMO) without "Configuration" repeated.
@dedemorton
Copy link
Contributor

Resolved in #3866

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants