[PR #548] Add Dozzle to Monitoring Section #1181

Closed
opened 2025-11-19 21:10:15 -06:00 by GiteaMirror · 0 comments
Owner

Original Pull Request: https://github.com/awesome-foss/awesome-sysadmin/pull/548

State: closed
Merged: No


This should close in awesome-selfhosted-data, 532 If there's any comments, concerns, questions please let me know!

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

  • Your additions are Free software
  • Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
  • Submit one item per pull request. This eases reviewing and speeds up inclusion.
  • Format your submission as follows, where Demo and Clients are optional.
    Do not add a duplicate Source code link if it is the same as the main link.
    Keep the short description under 80 characters and use sentence case
    for it, even if the project's webpage or readme uses another capitalisation.
    Demo links should only be used for interactive demos, i.e. not video demonstrations.
    - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
  • Additions are inserted preserving alphabetical order.
  • Additions are not already listed at awesome-selfhosted
  • The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
  • You have searched the repository for any relevant issues or PRs, including closed ones.
  • Any category you are creating has the minimum requirement of 3 items.
  • Any software project you are adding to the list is actively maintained.
  • The pull request title is informative, unlike "Update README.md".
    Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
    "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

  • Why is it awesome?

It's awesome since it can thoroughly analyze your docker logs in real-time to see if there's issues.

  • Have you used it? For how long?

I have used it before and for a while to test it out and will do it again if the situation arises.

  • Is this in a personal or professional setup?

This was in a personal setup for my homelab. I even made a dedicated subdomain for it.

  • How many devices/users/services/... do you manage with it?

A few docker containers at best, I can increase it when necessary if resources allow

  • Biggest pros/cons compared to other solutions?

Portainer/Yacht etc are more pretty and can easily whip up a docker container in a snap, but this one is more straightforward in just monitoring your logs and for diagnosis.

  • Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
    N/A
**Original Pull Request:** https://github.com/awesome-foss/awesome-sysadmin/pull/548 **State:** closed **Merged:** No --- This should close in awesome-selfhosted-data, [532](https://github.com/awesome-selfhosted/awesome-selfhosted-data/issues/532) If there's any comments, concerns, questions please let me know! <!-- DO NOT DELETE THE TEXT BELOW. Please make sure relevant boxes are checked [x] --> Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [X] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [X] Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [X] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [X] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [X] Additions are inserted preserving alphabetical order. - [X] Additions are not already listed at [awesome-selfhosted](https://github.com/awesome-selfhosted/awesome-selfhosted) - [X] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [X] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [ ] Any category you are creating has the minimum requirement of 3 items. - [X] Any software project you are adding to the list is actively maintained. - [X] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- Please take some time to answer the following questions as best you can: <!-- Failure to answer these questions in a useful and unbiased way will result in your submission being rejected. --> - **Why is it awesome?** It's awesome since it can thoroughly analyze your docker logs in real-time to see if there's issues. - **Have you used it? For how long?** I have used it before and for a while to test it out and will do it again if the situation arises. - **Is this in a personal or professional setup?** This was in a personal setup for my homelab. I even made a dedicated subdomain for it. - **How many devices/users/services/... do you manage with it?** A few docker containers at best, I can increase it when necessary if resources allow - **Biggest pros/cons compared to other solutions?** Portainer/Yacht etc are more pretty and can easily whip up a docker container in a snap, but this one is more straightforward in just monitoring your logs and for diagnosis. - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** N/A
GiteaMirror added the pull-request label 2025-11-19 21:10:15 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#1181