We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What did you do?
Running consul_exporter with one of the log.format parameter examples from the docs:
./consul_exporter --log.format "logger:syslog?appname=bob&local=7"
What did you expect to see?
Logs sent to syslog
What did you see instead? Under which circumstances?
consul_exporter crashes:
consul_exporter: error: unrecognized log format "logger:syslog?appname=bob&local=7", try --help
Cause I think this is caused by the change of logging library: #144
I can't see any easy way to configure the new library so send logs to syslog. Are there some secret environment variables now?
It looks like go-kit supports syslog output: https://github.com/go-kit/log/blob/main/syslog/syslog.go
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What did you do?
Running consul_exporter with one of the log.format parameter examples from the docs:
What did you expect to see?
Logs sent to syslog
What did you see instead? Under which circumstances?
consul_exporter crashes:
Cause
I think this is caused by the change of logging library: #144
I can't see any easy way to configure the new library so send logs to syslog. Are there some secret environment variables now?
It looks like go-kit supports syslog output: https://github.com/go-kit/log/blob/main/syslog/syslog.go
The text was updated successfully, but these errors were encountered: