Hello heka people!
We have a kibana/elasticsearch stack already running (with custom json
formats), and I'd like to massage the message coming out of some JSON inputs we
have to not exactly follow the Heka message format. Specifically, I'd like the
JSON contained in the "@message" value to move up a level, so that _source
directly contains my relevant keys, like so:
{"_source": {
"@uuid": <guid here>,
"@timestamp": <timestr here>,
"@ID": <my custom guid>,
"@status": <custom status>
}
I was thinking at first that I could create a lua encoder, but looking at the
API I don't see anything where I can modify the output directly. I can modify
the payload, or I can modify the message, but I can't go outside the schema of
the Heka message (at least that's my impression).
Do I need to create a Sandbox Output to do this? Or copy the ElasticSearch go
output and tweak it? Hopefully my question makes sense. We can get what we want
if we use logstash, but we love go and heka seems awesome.
Thanks for any guidance!
Steve Lewis
Sr. Software Engineer
PETNET Solutions, Inc.
This message and any attachments are solely for the use of intended recipients.
The information contained herein may include trade secrets, protected health or
personal information, privileged or otherwise confidential information.
Unauthorized review, forwarding, printing, copying, distributing, or using such
information is strictly prohibited and may be unlawful. If you are not an
intended recipient, you are hereby notified that you received this email in
error, and that any review, dissemination, distribution or copying of this
email and any attachment is strictly prohibited. If you have received this
email in error, please contact the sender and delete the message and any
attachment from your system. Thank you for your cooperation
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka
