If a field isn't found, the field interpretation string is sent to influxdb

[Ultimation]

• Version:
  logstash-5.4.1-1.noarch
  logstash-output-influxdb (5.0.0)
• Operating System:
  Centos 7.2
• Config File (if you have sensitive info, please remove it):

influxdb {
  host => "localhost"
  db => "logstash"
  data_points => {
    "always_exists" => "%{[fielda][fieldb]}"
    "sometimes_exists" => "%{[fielda][fieldc]}"
  }
}

I have a range of data points in my config, some of which don't always exist.
When they don't exist, I don't want the plugin to send anything. Instead it will send "%{[fielda][fieldc]}" into the influx database as a string.

I can get around this by having multiple modules instantiated in the config file for each situation, but sending the string interpretation seems wrong.

[IngaFeick]

Ran into the same issue a couple of days ago. I am currently testing a patch, might send a PR in a couple of days.

[Ultimation]

Have we got any progress on this? I'm noticing it also happening on empty strings in fields too now

[trondvh]

+1