-
Notifications
You must be signed in to change notification settings - Fork 878
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
Docs: Pino Logging with Grafana Promtail/Loki #1932
Comments
Would you like to add a link to that page in our help section? I've used pino-loki with great satisfaction as well. |
pino-loki is really well made but as explained in the article it follows a different paradigm. In our setup a service should not be concerned with log consumption, much less be tied to a loki instance/config. Regarding the link, I'd be happy to add a PR. Wanted to make sure it's useful first. 🙂 |
This adds helpful information a the usecase of using the Grafana monitoring stack for evaluating pino logs. Resolves pinojs#1932
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I recently spent way to much time to get Promtail and Loki to consume our pino logs in a way that I found satisfactory.
Since logs, which aren't processed or read by anything are basically useless, this should be fairly common challenge.
Information about setting this up properly is surprisingly hard to find, which is why, when I finally made it work, I decided to write an article about it.
I humbly present it here, A for feedback and B so it might be helpful to other pino users.
https://medium.com/@janpaepke/structured-logging-in-the-grafana-monitoring-stack-8aff0a5af2f5
If the maintainers agree this may be useful information, we could also consider linking it in the package docs somewhere.
The text was updated successfully, but these errors were encountered: