-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add index pattern, rename index options #2074
Labels
Comments
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Jul 21, 2016
The "index" setting name has historical reasons, from the times that all outputs shared the same configuration options. Since the meaning and contents of the "index" setting are starting to vary per output, it's time to clean this up. The Redis "index" is now called "key". Before this change, the index was still somehow special, since it was set to the beatName outside of the output. This removes this hack, and sets index to beatName only in the Elasticsearch and Logstash modules. This also removes the `index` setting for the file output, but that was never documented. Part of elastic#2074.
Closed
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Jul 21, 2016
This transforms the fixed index into a pattern, somehow similar to how Logstash is doing it. However, logstash is using the Joda format, for which we don't have Go libraries. So instead of writing `filebeat-%{+YYYY.MM.dd}` you would need to write `filebeat-%{+2006.01.02}` (i.e. layout by example). Because the Go layouts don't support ISO 8601 weeks, in order to support weekly indices, the special `isoweek` keyword was introduced, which is the equivalent of Joda `xxxx.ww`. The layout `filebeat-%{+isoweek}` results in `filebeat-2016.29` for today. Part of elastic#2074. Closes elastic#921.
tsg
pushed a commit
to tsg/beats
that referenced
this issue
Jul 21, 2016
The "index" setting name has historical reasons, from the times that all outputs shared the same configuration options. Since the meaning and contents of the "index" setting are starting to vary per output, it's time to clean this up. The Redis "index" is now called "key". Before this change, the index was still somehow special, since it was set to the beatName outside of the output. This removes this hack, and sets index to beatName only in the Elasticsearch and Logstash modules. This also removes the `index` setting for the file output, but that was never documented. Part of elastic#2074.
urso
pushed a commit
that referenced
this issue
Jul 25, 2016
The "index" setting name has historical reasons, from the times that all outputs shared the same configuration options. Since the meaning and contents of the "index" setting are starting to vary per output, it's time to clean this up. The Redis "index" is now called "key". Before this change, the index was still somehow special, since it was set to the beatName outside of the output. This removes this hack, and sets index to beatName only in the Elasticsearch and Logstash modules. This also removes the `index` setting for the file output, but that was never documented. Part of #2074.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Meta issue for transforming the Elasticsearch output index option into an index pattern (#921) and for cleaning up the outputs configuration around indices.
Tasks:
index
option tokey
, deprecatingindex
for now. Renamed redis.index option to redis.key #2077.index
option. Renamed redis.index option to redis.key #2077index
accept an index pattern Configurable Elasticsearch index pattern #2119The text was updated successfully, but these errors were encountered: