📢 v9 release coming -- Feedback needed!

[amir20]

Hi everyone!

Happy new year. I am preparing for v9 release. There are big improvements coming:

Changes to home page

• Homepage redesign to use historical stats everywhere.
• Host card has been redesign to track historical stats across all containers feat: support historical stats on homepage, hosts and containers.  #4307
• Home page is now more customizable with collapsible sections feat: allows homepage to have collopasable sections #4315

Changes to container page

• D3 has been completely removed in favor of simple bars
• Use the new stat view on container with similar colors

Changes to menu

• Added group counters on side menu feat: adds group counter for containers in menu #4313
• Adding new namespace drop down for k8s mode feat: adds k8s menu and sets it to default in k8s mode #4325
• Defaulting swarm menu when in swarm mode

Changes to log

• Logs are now grouped together when they are successfully have a level and part of the same message feat: support grouping of log messages when possible #4320
• Copy grouped messages together for easier copy and pasting

Bugs & Performance

• Fixes log level of "warning" not working fix: fixes upper case levels not working in the middle of log #4323
• Fixes performance on homepage perf: improves performance on the homepage #4324
• Updated DuckDb

Please try amir20/dozzle:master and provide feedback here.

[amir20]

[amir20]

Releasing v9! Test it out and provide feedback here 🙏

[homelab-alpha]

Hi @amir20,

First of all, I’d like to wish you a happy New Year as well.

I want to share some feedback, and unfortunately it’s not entirely positive but I hope it’s received in the constructive spirit in which it’s intended.

In my view, Dozzle is starting to resemble projects like Beszel. Please don’t take this the wrong way: the main reason I use Dozzle is precisely because of its simplicity. It focuses on logs and basic CPU and RAM usage, which makes it very easy to get a quick, at-a-glance understanding of what’s happening in a container or cluster.

Recently, however, more features have been added. Some of these are certainly convenient, but others feel unnecessary and add visual and cognitive complexity. Examples include collapsible sections and real-time metrics with many different colors. Together, these changes make the interface feel more crowded, whereas Dozzle originally stood out for being lightweight and straightforward.

As more functionality is introduced, some parts of the UI also seem to work less smoothly. One example is the scaling behavior on the homepage, which I’ve highlighted in the attached screenshots.

I’d also like to mention the use of colors for host metrics CPU in green and RAM in yellow. These choices can be problematic in a few ways:

• For users with color blindness, green and yellow can be difficult to distinguish. This article explains the issue well: 8 Colors to Avoid for Color Blindness in Web Design.
• Beyond accessibility, the semantic meaning of these colors can be confusing. Green typically signals “everything is fine,” while yellow often implies a warning or something that needs attention, which may not be the intended message here.

Overall, my concern is that Dozzle is gradually losing some of the simplicity that originally made it so appealing. I truly appreciate the work that goes into maintaining and improving the project, and I hope this feedback can be useful when thinking about future direction and design decisions.

Thanks for taking the time to read this, and I’d be interested to hear your thoughts.

screenshots (click to expand)

Display size	Screenshot
MacBook Air 13-inch
Desktop Monitor 27-inch

[amir20]

Thanks for the feedback. I always appreciate both positive and constructive input.

Let me reassure you that I do not want Dozzle to be complicated. I receive an enormous number of feature requests every day. I constantly say no to these requests because I want Dozzle to focus on doing one thing well: prioritizing quality over quantity. Dozzle is an investigation tool for Docker containers, and I do not plan to add features for starting containers, reading server stats, etc.

Now, to address some of the comments, a bit of context would be helpful. Recently, I built a home media server for downloading Linux images. 😄 I set up the *arr stack, and during this process, several things broke. I used Dozzle extensively to stream logs, check stats, and investigate issues. I had not done this before with the *arr stack. I noticed that Dozzle lacked functionality to help me solve my own problems. For example, my CPU was spiking across multiple containers, but I didn't have a good way to identify which one was causing it. As a result, I thought about how Dozzle could improve its reporting to highlight potential issues.

As an engineer, I focus on understanding the problem rather than jumping to solutions. The features added in v9 were designed to address some challenges I faced while setting up new applications. I don't believe I introduced anything that falls outside the scope of Dozzle.

Now, to respond to some specific points:

One example is the scaling behavior on the homepage, which I’ve highlighted in the attached screenshots.

I'm not sure what you mean. If this is a bug, it should be fixed. Since this is a new feature, there may be bugs. The challenge I face is that when I ask people to test, they often wait until after I release it to provide feedback. 🤷

For users with color blindness, green and yellow can be difficult to distinguish. This article explains the issue well: 8 Colors to Avoid for Color Blindness in Web Design.

I am aware of color blindness. I did not introduce any new colors; I aimed for consistency so that it is immediately clear which chart represents CPU or memory. The same color scheme is used on the container page for consistency. I believe this approach reduces the mental load of reading labels.

Beyond accessibility, the semantic meaning of these colors can be confusing. Green typically signals “everything is fine,” while yellow often implies a warning or something that needs attention, which may not be the intended message here.

Dozzle uses two colors: the primary color for CPU, which is used everywhere, and yellow as the secondary color. For errors, I use red or orange.

Overall, my concern is that Dozzle is gradually losing some of the simplicity that originally made it so appealing. I truly appreciate the work that goes into maintaining and improving the project, and I hope this feedback can be useful when thinking about future direction and design decisions.

To summarize, I have no intention of making Dozzle complicated. It remains a ~15MB container focused on logs, reading stats, and debugging when needed.

If the colors can be improved, please send pull requests. However, I have tested on multiple screens, and it looked fine.

[homelab-alpha]

I'm not sure what you mean. If this is a bug, it should be fixed. Since this is a new feature, there may be bugs. The challenge I face is that when I ask people to test, they often wait until after I release it to provide feedback. 🤷

Sorry, I forgot to mark and crop the screenshots.

What I mean is that the information no longer fits entirely on the screen. To see everything, you now need to either scroll horizontally or hide the left sidebar so that the container information becomes fully visible.

screenshots (click to expand)

---

I am aware of color blindness. I did not introduce any new colors; I aimed for consistency so that it is immediately clear which chart represents CPU or memory. The same color scheme is used on the container page for consistency. I believe this approach reduces the mental load of reading labels.

What I meant is that it can be difficult for people with color blindness to read the charts because the same information is conveyed solely through color. In the RAM usage chart, combinations like yellow on yellow or light gray on yellow are hard to distinguish and therefore difficult to read. The same principle applies to the CPU chart, where combinations like green on green and light gray on green are also difficult to distinguish.

screenshots (click to expand)

---

Dozzle uses two colors: the primary color for CPU, which is used everywhere, and yellow as the secondary color. For errors, I use red or orange.

My comment only concerned the GPU and RAM charts, not the other colors used, for example, in the logs.

---

To summarize, I have no intention of making Dozzle complicated. It remains a ~15MB container focused on logs, reading stats, and debugging when needed.

I’m glad to hear that, because it is precisely Dozzle’s simplicity and clarity that make it so easy to use.

---

If the colors can be improved, please send pull requests.

I’m currently working on a project myself and also find it challenging to create a color palette that provides a good experience for people with color blindness when it comes to color themes and charts. So far, I haven’t fully figured out what really works well in terms of colors.

[amir20]

The first issue is definitely a bug. Let me create a new issue. The host menu only shows when there are multiple hosts which is why I didn't notice it before.

[amir20]

OK crested #4333

As for other, it's mostly about colors. No one has complained about colors yet :)

I’m currently working on a project myself and also find it challenging to create a color palette

I am not a designer either. However, Figma has a free option where you can use AI to ideate on designs. That design was actually a brainstorming session I did with Figma. You can try it out with screenshots.