Re: [PATCH] MINOR: promex: Introduce 'FULL' status for srv_state metric

On Mon, Sep 11, 2023 at 08:39:30PM +0200, Christopher Faulet wrote: > Le 11/09/2023 à 15:12, Cedric Paillet a écrit : > > This adds a new 'FULL' status to the Prometheus metric 'srv_state'. It > > helps identify servers that have exceeded their maxconn limit and cannot > > accept new

Re: [PATCH] MINOR: promex: Introduce 'FULL' status for srv_state metric

Le 11/09/2023 à 15:12, Cedric Paillet a écrit : This adds a new 'FULL' status to the Prometheus metric 'srv_state'. It helps identify servers that have exceeded their maxconn limit and cannot accept new connections. Rename server_has_room to !server_is_full to matches what's used at a few

Re: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

Le 07/09/2023 à 16:50, Cedric Paillet a écrit : And I guess we should also check the healthchecks are enabled for the server. It is not really an issue because call to get_check_status_result() will exclude neutral and unknown satuses. But there is no reason to count these servers. What

Re: [PATCH] BUG/MINOR: promex: don't count servers in maintenance

Le 11/09/2023 à 15:09, Cedric Paillet a écrit : The state of servers that were put in maintenance via the runtime API are reported within the "backend_agg_check_status" metric, which lead to inconsistent sums when compared to the "haproxy_server_check_status" metric. Now excluding them from

Re: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Alexander, On Mon, Sep 11, 2023 at 03:44:16PM +, Stephan, Alexander wrote: > Hi Willy and Ilya, > > Sorry for the absence, I was mostly out-of-office the last week. I am really > sorry for causing this bug. No worries, stuff like this happens, that's why we have regtests, CI, this

RE: [PATCH] MEDIUM: sample: Implement sample fetch for arbitrary PROXY protocol v2 TLV values

Hi Willy and Ilya, Sorry for the absence, I was mostly out-of-office the last week. I am really sorry for causing this bug. Thanks so much Willy for fixing it as well as for the pool inspection feature I saw today, that looks really handy. I actually debugged the code for quite some time as

Re: Odd bwlim Behavior

Le 08/09/2023 à 14:51, Luke Seelenbinder a écrit : Hi Christopher, I just tried with a single limit on a single table (50m per 10s). Unfortunately, it looks like the behavior persists. Interestingly enough…the an_exp in this case is now 12m! Hi Like, 12min is amazingly high ! Could you

[PATCH] MINOR: promex: Introduce 'FULL' status for srv_state metric

This adds a new 'FULL' status to the Prometheus metric 'srv_state'. It helps identify servers that have exceeded their maxconn limit and cannot accept new connections. Rename server_has_room to !server_is_full to matches what's used at a few places in the doc in association with servers or

[PATCH] BUG/MINOR: promex: don't count servers in maintenance

The state of servers that were put in maintenance via the runtime API are reported within the "backend_agg_check_status" metric, which lead to inconsistent sums when compared to the "haproxy_server_check_status" metric. Now excluding them from this computation. ---

Coordinating design services for haproxy.com.

Hey *haproxy.com *Team, I can completely develop your website and give it a fresh and innovative look as well as make it *user-friendly*. I assure you that you will help you beat your competitors by using *trending technologies*. Wanna give us a chance to *develop *your