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
Using osctrlv0.1.8, using logging = "graylog" in the service configuration (tls.json) for osctrl-tls, using Graylog's HTTP GELF receiver, messages that are group in JSON dictionaries are not accepted.
Steps to reproduce
1 - Set logging to graylog, logging = "graylog" in tls.json
2 - Create graylog HTTP GELF input.
3 - Generate logs
GELF seems to expect individual log statements in JSON {GELF_OBJ}. The osctrl graylog plugin is grouping logs together, and the final document being sent to graylog is [{GELF_OBJ},{GELF_OBJ},{GELF_OBJ},...], which evidently is not cool. This was validated via test GELF messages and tcpdump to view the raw texts to graylog - it dumps them silently otherwise.
To resolve this, I removed the grouping components of the plugin, and send a request for each log.
I haven't used Graylog much, so maybe I've missed something, but the message won't even make it to an index - it gets dropped.
The text was updated successfully, but these errors were encountered:
I see how this is a problem. Sending one request per log line, it may impact performance but at least Graylog may be able to ingest data. Do you want to put together a PR with the changes you made? Thanks!
Issue
Using
osctrl
v0.1.8
, usinglogging = "graylog"
in the service configuration (tls.json
) forosctrl-tls
, using Graylog's HTTP GELF receiver, messages that are group in JSON dictionaries are not accepted.Steps to reproduce
1 - Set logging to graylog,
logging = "graylog"
intls.json
2 - Create graylog HTTP GELF input.
3 - Generate logs
GELF seems to expect individual log statements in JSON
{GELF_OBJ}
. The osctrl graylog plugin is grouping logs together, and the final document being sent to graylog is[{GELF_OBJ},{GELF_OBJ},{GELF_OBJ},...]
, which evidently is not cool. This was validated via test GELF messages and tcpdump to view the raw texts to graylog - it dumps them silently otherwise.To resolve this, I removed the grouping components of the plugin, and send a request for each log.
I haven't used Graylog much, so maybe I've missed something, but the message won't even make it to an index - it gets dropped.
The text was updated successfully, but these errors were encountered: