Implement Loki Logging Properly #31
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
With a better understanding and better personal documentation, we can design and implement Loki logging properly.
Tasks
References
mentioned in commit
54124da9d1
Re: Build list of services to add logging to
Fuck that. I just did it. See:
54124da9
marked the checklist item Build list of services to add logging to as completed
Re: Document process for instrumenting Loki logging for a new app
See: https://gitlab.jafner.net/Jafner/homelab/-/blob/main/server/config/monitoring/README.md
marked the checklist item Document process for instrumenting Loki logging for a new app as completed
mentioned in commit
241d798f9e
marked the checklist item Update basic webapp template with new logging instrumentation as completed
Re: Find out what happens when the logging endpoint is down. Does the application still work? Is the system stable?
Ran a
docker stop monitoring_loki
and then waited a while (30s) for errors to accumulate. Checkedsudo systemctl status docker.service
and confirmed error messages in the logs. Applications remained available. Docker still responds to commands to manipulate other containers.marked the checklist item Find out what happens when the logging endpoint is down. Does the application still work? Is the system stable? as completed