Add Elasticsearch indexes variable ... #8
Closed
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.
... to avoid querying indexes which do not have the expected document fields.
Problem description
When queries are run against the Elasticsearch cluster, no index option is provided. In this case, the underlying library defaults to "_all". This is problematic when the ES cluster has indexes which don't contain documents with the field @timestamp. An Exception is raised by Elasticsearch like the example below: (query masked for privacy reasons)
Fix
By explicitly providing the list of indexes to run the query against, the above error is avoid. The indexes variable is optional for the logstash configuration. If the variable is not set in the configuration, an empty string is supplied by the plugin and the underlying library will use the original behaviour of querying "_all".