You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain ill-mannered programs (I'm looking at you, docker-registry) emit JSON-formatted log entries, but use dot-delimited nesting in the key names, which breaks with ES 2.x. Since the JSON emitted by these programs isn't necessarily intended to be consumed by logstash, it's not necessarily their fault that they're producing logstash-incompatible JSON, but is instead logspout-logstash's responsibility to transmute the error-producing JSON into something that logstash will understand.
I can think of two options:
Replace all dots in keys with underscores (quick, dirty, and within my extremely limited Go skills to implement); or
Translate dot-encoded keys into a nested structure (far superior, but there's no way known I can implement that all by myself).
Would a PR to implement option 1 be merged, or should I wait for someone with better Go chops to implement 2?
The text was updated successfully, but these errors were encountered:
Yes, it's still an issue. Option 2 would be a better outcome, by far, because it maintains structure, but someone else would have to implement it because I've got near-zero Go skills. I could do a PR for option 1, though, if nobody else has the time to code something better.
Certain ill-mannered programs (I'm looking at you,
docker-registry
) emit JSON-formatted log entries, but use dot-delimited nesting in the key names, which breaks with ES 2.x. Since the JSON emitted by these programs isn't necessarily intended to be consumed by logstash, it's not necessarily their fault that they're producing logstash-incompatible JSON, but is instead logspout-logstash's responsibility to transmute the error-producing JSON into something that logstash will understand.I can think of two options:
Would a PR to implement option 1 be merged, or should I wait for someone with better Go chops to implement 2?
The text was updated successfully, but these errors were encountered: