Hey, I added a patch to the GitHub issue that explicitly sets a color for this case.
I just took the same color as for backend servers that don't have a health check assigned. This definetely improves the situation and makes information readable again. It would be nice to have the patch applied and Ciprian on GitHub already asked for a backport to 2.5. Is it enough to send the patch to this mailing list? Thanks a lot Marno Am 08.03.22, 13:30 schrieb "Tim Düsterhus" <[email protected]>: Ciprian, On 3/8/22 12:57, Ciprian Craciun wrote: > I've forgotten the screenshot... :) see: https://github.com/haproxy/haproxy/issues/1461 Best regards Tim Düsterhus
From 74bc376bb290d50b5fd140a8f8f8d87f59899322 Mon Sep 17 00:00:00 2001 From: Marno Krahmer <[email protected]> Date: Tue, 8 Mar 2022 13:45:09 +0100 Subject: [PATCH] MINOR: stats: Add dark mode support for socket rows In commit e9ed63e548 dark mode support was added to the stats page. The initial commit does not include dark mode color overwrites for the .socket CSS class. This commit colors socket rows the same way as backends that acre active but do not have a health check defined. This fixes an issue where reading information from socket lines became really hard in dark mode due to suboptimal coloring of the cell background and the font in it. --- src/stats.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/stats.c b/src/stats.c index d15ce094d..f044588d4 100644 --- a/src/stats.c +++ b/src/stats.c @@ -3332,6 +3332,7 @@ static void stats_dump_html_head(struct appctx *appctx, struct uri_auth *uri) " .hr { border-color: #8c8273; }\n" " .titre { background-color: #1aa6a6; color: #e8e6e3; }\n" " .frontend {background: #2f3437;}\n" + " .socket {background: #2a2d2f;}\n" " .backend {background: #2f3437;}\n" " .active_down {background: #760000;}\n" " .active_going_up {background: #b99200;}\n" -- 2.32.0 (Apple Git-132)
