-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
input from nginx error_log show unsupported version #18
Comments
Hi, And thanks for using Flowgger! I would recommend using a structured format such as ltsv, which works really well with Nginx, instead of syslog messages, whose format vary according to the syslog daemon and its configuration. What does a line of log look like? |
The system syslog daemon on macOS still uses the very old RFC3164 format, that got obsolete with RFC5424. The old format has limitations. Timestamps cannot be reliably parsed, and payloads are limited to strings. Key/value pairs are not supported. Flowgger doesn't support the old format, only the RFC5424 one, which is supported by common logging daemons such as rsyslogd. Still, even RFC5424 is terrible. Slow, complicated and limited. Use LTSV. |
Thanks you for quick response. This is the example of error.log
after search for a while, i found that nginx generate 2 log files My use case is to create a centralized logging system from many nginx servers. Right now my solution is
run command
it is not the best solution but good enough for my use case Thanks you for your great work |
* File rotation implementation, unit test coverage improved, reformatting * Use of temp dir for file testing * Updating package version and comments * Increased file rotation limit and clarified comments in config
I use nginx-1.12.0 version and flowgger-master on macOS 10.12.4
in the nginx configuration file
nginx.conf
, I instruct nginx to send error log to local syslog serverin
flowgger.toml
after I recompile and restart flowgger, start nginx and make some error to generate a error log
Do you have a plan to support input nginx log (both
error_log
andaccess_log
)?The text was updated successfully, but these errors were encountered: