[Feature Request] Add an Optional "Health" Column to Container Listings

[s4l1mz]

Description

First of all, thank you to the Komodo team for the continued development of this excellent project. Komodo has become a very useful tool for managing and monitoring Docker infrastructure, and this feature request is intended as a small UI improvement that could make day-to-day container monitoring even more convenient.

I would like to suggest adding an optional Health column to the container listings in the following two locations:

1. Global "Containers" page — the page that lists containers across all connected Servers.
2. Server → Docker tab — the container list displayed when viewing the Docker resources of a specific Server.

The information is already available when opening an individual container, where Komodo displays its Docker health status (for example, HEALTHY). The suggestion is simply to expose the same information directly in the container tables.

Current behavior

At the moment, the container lists provide useful information such as:

• Name
• Server
• State
• Image
• Networks
• Ports
• Volumes

However, the container's Docker health status is not directly visible in these tables.

To determine whether a running container is actually healthy, the user currently needs to open the individual container and inspect its details.

This creates an important distinction that is not immediately visible in the list:

RUNNING

does not necessarily mean:

RUNNING + HEALTHY

A container may be running normally from Docker's perspective while its application is failing its configured HEALTHCHECK.

Proposed improvement

Add a configurable Health column to both container listing views:

Name | Server | State | Health | Image | Networks | Ports | Volumes

The column could display the Docker health status, for example:

HEALTHY
UNHEALTHY
STARTING
—

where — would indicate that the container does not define a Docker HEALTHCHECK.

The health status should remain independent from the existing State column, since they represent different aspects of the container:

State	Health	Meaning
RUNNING	HEALTHY	Container is running and the healthcheck is passing
RUNNING	UNHEALTHY	Container is running, but the healthcheck is failing
RUNNING	STARTING	Healthcheck is still initializing
RUNNING	—	No healthcheck is configured
EXITED	—	Container is stopped

Optional / configurable columns

Ideally, the new Health column would follow the same approach as other table columns and be optional/configurable by the user.

For example, users could choose which columns they want to display:

☑ Name
☑ Server
☑ State
☑ Health
☑ Image
☐ Networks
☐ Ports
☐ Volumes

This would avoid making the tables unnecessarily wide while still allowing users who rely heavily on Docker healthchecks to keep the information permanently visible.

Why this would be useful

This would provide a much faster way to identify unhealthy applications without opening containers one by one.

For example, a container list could immediately show:

nginx        RUNNING   HEALTHY
postgres     RUNNING   HEALTHY
api          RUNNING   UNHEALTHY
redis        RUNNING   HEALTHY
worker       RUNNING   STARTING

This would be particularly useful for larger environments and for the global Containers view, where operators may need to quickly identify problematic containers across multiple Servers.

It would also make the distinction between process state and application health much more apparent.

Scope

The requested improvement would apply to both:

• Containers → global container listing
• Servers → [Server] → Docker → Containers

The same Health column and the same column-visibility mechanism would ideally be available in both locations for consistency.

Expected behavior

After this improvement, users should be able to:

1. See the Docker health status directly in container tables.
2. Distinguish between RUNNING and RUNNING + HEALTHY.
3. Identify UNHEALTHY containers without opening each container individually.
4. Optionally enable or disable the Health column according to their preferred table layout.
5. Have the same behavior in both the global Containers page and the Server → Docker container list.

Thank you very much for considering this suggestion. I believe it would be a relatively small UI enhancement with a meaningful operational benefit, especially for users managing larger Docker environments.

Thank you again for all the work put into Komodo!