Hi,
Just want to let everyone know that I've been working on converting the
ElasticSearchOutput from using its custom 'format' configuration setting
to instead using the new encoder plugin infrastructure that will be in
the upcoming 0.6 release.
In v0.5.2, the two most (only?) used formats were "clean" (generating a
nicely formatted JSON representation of each message) and "logstash_v0"
(generating a JSON representation matching the original "v0" schema used
by Logstash). In 0.6, there will be an ESJsonEncoder and an
ESLogstashV0Encoder which generate the same output, delta a few bug fixes.
In the process, the config options for the ElasticSearchOutput itself
were cleaned up a bit.
To give you an idea about the changes to expect, a v0.5.2 config section
like this:
[ElasticSearchOutput]
message_matcher = "Type == 'nginx.access'"
index = "%{Type}-%{2006.01.02}"
type_name = "%{Type}"
server = "http://es-server:9200";
format = "clean"
esindexfromtimestamp = true
flush_interval = 5000
flush_count = 10
Would in v0.6 look like this:
[ESJsonEncoder]
index = "%{Type}-%{2006.01.02}"
es_index_from_timestamp = true
type_name = "%{Type}"
[ElasticSearchOutput]
message_matcher = "Type == 'nginx.access'"
encoder = "ESJsonEncoder"
server = "http://es-server:9200";
flush_interval = 5000
flush_count = 10
This change will be merged to dev momentarily. As always, feel free to
ask questions on this mailing list or in one of our #heka IRC channels
(on irc.freenode.net or irc.mozilla.org) if you have any issues.
Thanks for Heka-ing!
-r
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
