All listeners should make it clear how they separate incoming events.
a) HTTP + JSON + array = one event per array element in the JSON in the HTTP POST
b) TCP = hard coded to break on newline (\n)
c) UDP = events arriving within a single packet arrive together in the parser
I'd like to see those defaults configurable. I'd like to be able to separate on different characters, or based on a regex, or a count of bytes.
I'd like the UI for testing the parser to show all events parsed, right now it only shows one when using my work around. Some parsers may or may not produce more than one event as an outcome, this should be visually obvious.
Your StatsD documentation is really not great and even a bit wrong. :) Below I've included an entire parser that supports the extended syntax for tags in events as well as just the metric.
Feature suggestion from BlockFi/Greg:
All listeners should make it clear how they separate incoming events. a) HTTP + JSON + array = one event per array element in the JSON in the HTTP POST b) TCP = hard coded to break on newline (\n) c) UDP = events arriving within a single packet arrive together in the parser
I'd like to see those defaults configurable. I'd like to be able to separate on different characters, or based on a regex, or a count of bytes.
I'd like the UI for testing the parser to show all events parsed, right now it only shows one when using my work around. Some parsers may or may not produce more than one event as an outcome, this should be visually obvious.
Your StatsD documentation is really not great and even a bit wrong. :) Below I've included an entire parser that supports the extended syntax for tags in events as well as just the metric.
For further information and ideas see related Zendesk ticket: https://humio.zendesk.com/agent/tickets/1858