-
|
Dozzle is fantastic for container logs. No doubt about that and I love it. I have light needs for non-container logging. This is for the most part logs from my wrapper around restic (a backup solution) or another of my apps not deployed with docker. Ideally I would just One is to write a proxy container that would transfer the incoming log to its console, and therefore ultimately to dozzle. One of the drawbacks of a proxy is that the logs will be inevitably attached to the name of the proxy container, right? (in other words, I cannot split on the left drawer by source). This si not the eond of the world, i would discriminate through a field in the log and filter on that |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @wsw70 ,
Dozzle is a simple wrapper around Docker API. It has no database. It is not capable of storing any logs. Docker stores logs on disk and exposes them over an API. Dozzle uses that API to paginate.
This has been discussed here https://dozzle.dev/guide/log-files-on-disk |
Beta Was this translation helpful? Give feedback.
Hi @wsw70 ,
Dozzle is a simple wrapper around Docker API. It has no database. It is not capable of storing any logs. Docker stores logs on disk and exposes them over an API. Dozzle uses that API to paginate.
This has been discussed here https://dozzle.dev/guide/log-files-on-disk