The hand-constructed JSON encoding used for the ESJsonEncoder is very useful for other situations that aren't just sending the data to an ElasticSearch bulk API endpoint. Unfortunately because of the presence of the ES index coordinate records, it means that in those cases there are a lot of records present in the stream that aren't useful. We, for example, use this encoding to send data to a few different logging outputs where we want the message JSON in this format, but don't want to have to throw out all the index coordinates. This PR introduces a configuration option to make sending the coordinates optional, but preserving the default behavior.
It should have no effect at all on the normal use case, but allows it to be more flexible for outputs to non-ES backends.
The hand-constructed JSON encoding used for the
ESJsonEncoderis very useful for other situations that aren't just sending the data to an ElasticSearch bulk API endpoint. Unfortunately because of the presence of the ES index coordinate records, it means that in those cases there are a lot of records present in the stream that aren't useful. We, for example, use this encoding to send data to a few different logging outputs where we want the message JSON in this format, but don't want to have to throw out all the index coordinates. This PR introduces a configuration option to make sending the coordinates optional, but preserving the default behavior.It should have no effect at all on the normal use case, but allows it to be more flexible for outputs to non-ES backends.