[GH-ISSUE #126] Meta-data #102

New issue

Open

opened 2026-02-26 05:31:20 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 05:31:20 +03:00

Owner

Originally created by @vmadman on GitHub (Aug 17, 2014).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/126

We use Log.io as a debugging utility for our Logstash (and soon, probably node-logstash) configurations. It's helpful to be able to see Logstash parsing results in real-time when trying to find where the chain is being disrupted.

Logstash's event format is JSON, and allows for an unlimited amount of metadata. For example, I can give an event a "hostname" field, or add tags such as "syslog" and "node-js-process".

Does Log.io currently offer an elegant way to expose message meta? Does @muchweb 's fork?

If no to both, has anyone else considered this? I'd gladly consider coding it myself if its likely that my pull request would be accepted.

Thanks,
Luke

Originally created by @vmadman on GitHub (Aug 17, 2014). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/126 We use Log.io as a debugging utility for our Logstash (and soon, probably node-logstash) configurations. It's helpful to be able to see Logstash parsing results in real-time when trying to find where the chain is being disrupted. Logstash's event format is JSON, and allows for an unlimited amount of metadata. For example, I can give an event a "hostname" field, or add tags such as "syslog" and "node-js-process". Does Log.io currently offer an elegant way to expose message meta? Does @muchweb 's fork? If no to both, has anyone else considered this? I'd gladly consider coding it myself if its likely that my pull request would be accepted. Thanks, Luke