I just started seeing this issue, I'm not quite sure what's up. I switched one of my environments to use the logstash+tcp functionality that recently got added to the logspout-logstash forwarder and noticed that an extra comma is being added to my custom tags. If the log doesn't hit a filter, the comma doesn't get added, and the tag column just stays blank like it should.
Here's an example of what the tags column looks like:
I've tried restarting the logspout-logstash forwarders, reverting back to the original configuration, and restarting logstash completely but the problem still persists.
Has this ever happened to anybody else? I'm not sure where to start troubleshooting this one.
What does the actual document in ES look like? Check the JSON tab in Kibana.
Here's an example of what the tags look like in the JSON view:
And another when the tag is empty:
Okay, so something's inserting empty tags. What does your configuration look like?
I looked through the config and couldn't find anything obvious.
The config is a bit of a bear so I will just link to the gist.
Indeed, nothing obvious. You could of course just remove the empty tag at the end.
Do you have a good example of how to do that (remove empty tags)?
remove_tag option of any filter (or a standalone mutate filter).
I'll give it a shot. Thanks!
For anybody else, the following pattern works.
remove_tag => [ "tags", ""]