Escape illegal '.' character before submitting data to ElasticSearch.

[ceilfors]

ElasticSearch is rejecting logstash-plugin data when an environment variable contains a '.' character. Specific problem encountered: When artifactory-plugin is used, the plugin will inject an environment variable called buildInfoConfig.propertiesFile.

[jakub-bochenski]

@ceilfors I tried to reproduce the issue with 1.2.1, but I can't

I've set VARIABLE.WITH.DOT via EnvInject and I see an

"_source": {
  "data":  {
    "buildVariables": {
        "VARIABLE.WITH.DOT": "foo",

entry in ES

[ceilfors]

The difference of the elasticsearch version we used might cause the problem. I can't remember which version I was using unfortunately as I have moved on to other projects.

…

On Wed, 10 May 2017, 18:53 jakub-bochenski, ***@***.***> wrote: @ceilfors <https://github.com/ceilfors> I tried to reproduce the issue with 1.2.1 I've set VARIABLE.WITH.DOT via EnvInject and I see an "_source": { "data": { "buildVariables": { "VARIABLE.WITH.DOT": "foo", entry in ES — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABRmlWxQ-BHIeJff35FjdQWGC2rGEdkTks5r4fmagaJpZM4LbrXB> .

[jakub-bochenski]

I think it worked in my setup because I'm actually using Logstash before the ES instance with the de_dot filter: https://www.elastic.co/blog/introducing-the-de_dot-filter

I think this is another reason for having a separate ES and Logstash indexer types instead of using the same for both

[jakub-bochenski]

@mwinter69 I think we should add this to the logstash tcp backed? I don't think it was included in #59

[mwinter69]

No, but this PR here is for Elastic Search. I think it should be optional.

[jakub-bochenski]

uh, right sorry I mixed the two up

[darxriggs]

Should this be closed as the author already moved on to other projects?

[jakub-bochenski]

The OP might have moved on, but the problem is still there. The challenge is to handle it while keeping it opt-in and without code duplication.