Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd flags to control logrus output destinations #785
Comments
juliusv
referenced this issue
Jun 10, 2015
Closed
Add flags to control logrus output destinations #4
This comment has been minimized.
This comment has been minimized.
|
This should be an issue in https://github.com/prometheus/log. Closing this one and opened a new one there: prometheus-junkyard/log#4 |
juliusv
closed this
Jun 10, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
wrouesnel commentedJun 10, 2015
The change to logrus has left prometheus without any easy way to be run on systems still using SysV init. This means at the moment Prometheus can only log to the console, which requires some hacky workarounds to get it playing nicely with init scripts.
Ideally there'd be a command line flag for something like
-log.hookto allow seeing the syslog, journald, file hooks logrus supports.