Elasticsearch 2.x no longer allows dot's in property names. Logstash has since added a de_dot[1] plugin to help users deal with this. We do not appear to have any need to do a full test/upgrade cycle on logstash as part of the es2.x upgrade, instead we should backport this plugin to the version of logstash we currently use.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | bd808 | T137400 Logstash elasticsearch mapping does not allow err.code to be a string | |||
Resolved | dcausse | T138608 Vagrant role provisions wrong elasticsearch version | |||
Resolved | debt | T136001 [EPIC] Upgrade elasticsearch cluster supporting logging to 2.3 | |||
Resolved | EBernhardson | T136003 Upgrade logstash*.eqiad.wmnet elasticsearch servers to 2.3 | |||
Resolved | EBernhardson | T138335 Backport de_dot plugin for logstash to 1.5.3 |
Event Timeline
Comment Actions
Change 295575 had a related patch set uploaded (by EBernhardson):
Add de_dot filter and rename to logstash-filters-wikimedia
Comment Actions
Change 295578 had a related patch set uploaded (by EBernhardson):
logstash: Utilize de_dot filter for sending to es 2.x
Comment Actions
Change 295575 merged by BryanDavis:
Add de_dot filter and rename to logstash-filters-wikimedia
Comment Actions
Mentioned in SAL [2016-06-27T17:23:22Z] <gehel> deploying new logstash config for transition to elasticsearch 2.x (T138335)
Comment Actions
Working in production since rOSLP18b3f1fe3d44: Fix de_dot to process keys with falsey values