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 upPrometheus Server Logs to Fluentd #4337
Comments
This comment has been minimized.
This comment has been minimized.
|
I don't feel that Prometheus needs to be modified to handle your use case. AFAIU it's up to you to setup your logging infrastructure to get the container logs and push them to your central location. |
This comment has been minimized.
This comment has been minimized.
|
yeah logging is displayed to stdout/stderr be default and it is up to the systemd or the container orchestrator to redirect the logs to wherever you decide. @mumarniaz this isn't something for us so I advise continuing on google search or other more relevant groups |
krasi-georgiev
closed this
Jul 3, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 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 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
mumarniaz commentedJul 3, 2018
Proposal
Currently, Prometheus server logs all logging information on
std::outto console. Is there any configuration or feature in prometheus server to send these logs to fluentd directly? I have found this plugin: Fluentd logging driver which run as a daemon set and send all pods logs to fluentd instead of only Prometheus server log.Use case. Why is this important?
It will be important in scenarios where someone want to place these logs on some centralize location and analyze those logs instead of getting it directly from Prometheus pod.