Hello Christopher,
Thank you for your quick answer.
On Mon, Nov 18, 2019 at 04:28:37PM +0100, Christopher Faulet wrote:
> Thanks. Having a way to filter metrics in the Prometheus exporter was on my
> todo-list :) Filtering on scopes is pretty simple and it is a good start to
> solve performance i
Le 16/11/2019 à 21:02, William Dauchy a écrit :
this patch is an attempt to permit parameters on the prometheus exporter
configuration: global, frontend, backend, listener, server.
This allows to avoid exporting metrics you don't necessary use. The
filtering can also be done on prometheus scrapin
On Wed, Nov 13, 2019 at 12:51:05PM -0500, N Seto wrote:
> Hi,
> We are looking for the official / reputable RPM for haproxy v 2.0.
> Can you suggest where we can obtain this?
>
> Best regards, N Seto
I just find out that someone is maintaining the RPMs on the IUS repository
(https://ius.io
On 11/18/19 2:40 PM, William Lallemand wrote:
> On Fri, Nov 15, 2019 at 06:49:10PM +0100, Willy Tarreau wrote:
>> On Wed, Nov 06, 2019 at 06:47:50PM +0100, Emmanuel Hocdet wrote:
>>> Hi,
>>>
>>> Very difficult to trigger the bug, except with spécific test configuration
>>> like:
>>> crt-list:
>>>
On Mon, Nov 18, 2019 at 2:37 PM Daniel Corbett wrote:
> Hello,
>
>
> On 11/18/19 7:05 AM, Willy Tarreau wrote:
> > On Mon, Nov 18, 2019 at 12:06:08PM +0100, Baptiste wrote:
> >> When we first designed this feature, we did it with this in mind "if
> admins
> >> can update a SRV record in a DNS ser
On Wed, Nov 06, 2019 at 06:47:50PM +0100, Emmanuel Hocdet wrote:
> Hi,
>
> Very difficult to trigger the bug, except with spécific test configuration
> like:
> crt-list:
> cert.pem !www.dom.tld
> cert.pem *.dom.tld
>
> If you can consider the patch.
>
> Thank's
> Manu
>
>
Pushed in master, t
On Wed, Nov 06, 2019 at 05:47:13PM +0100, Emmanuel Hocdet wrote:
> Hi,
>
> If you can consider the patch (related to CLI cert update)
>
> Thank's
> Manu
>
Pushed in master, thanks.
--
William Lallemand
On Fri, Nov 15, 2019 at 06:49:10PM +0100, Willy Tarreau wrote:
> On Wed, Nov 06, 2019 at 06:47:50PM +0100, Emmanuel Hocdet wrote:
> > Hi,
> >
> > Very difficult to trigger the bug, except with spécific test configuration
> > like:
> > crt-list:
> > cert.pem !www.dom.tld
> > cert.pem *.dom.tld
> >
Hello,
On 11/18/19 7:05 AM, Willy Tarreau wrote:
On Mon, Nov 18, 2019 at 12:06:08PM +0100, Baptiste wrote:
When we first designed this feature, we did it with this in mind "if admins
can update a SRV record in a DNS server, they can adjust the weight
accordingly".
I understand the need, but t
On Mon, Nov 18, 2019 at 12:06:08PM +0100, Baptiste wrote:
> When we first designed this feature, we did it with this in mind "if admins
> can update a SRV record in a DNS server, they can adjust the weight
> accordingly".
>
> I understand the need, but the response is way too short. It's a global
On Mon, Nov 18, 2019 at 11:57 AM Willy Tarreau wrote:
> Hi Daniel,
>
> On Sun, Nov 17, 2019 at 10:06:32AM -0500, Daniel Corbett wrote:
> > Hello,
> >
> >
> > I realize that new features are not preferred at the moment but I think
> this
> > might be a usability issue and hopefully it can be consi
Hi Daniel,
On Sun, Nov 17, 2019 at 10:06:32AM -0500, Daniel Corbett wrote:
> Hello,
>
>
> I realize that new features are not preferred at the moment but I think this
> might be a usability issue and hopefully it can be considered for 2.1-dev,
> however, it's perfectly fine if it's decided to wa
Hello list,
I'm currently trying to migrate our stack from haproxy 1.7 to 2.0 and
hit an issue with device detection.
We are using 51-Degrees for device detection. Our haproxy-1.7 instances
are built with the 51-degrees v3.2.10 branch, the relevant config looks
like this:
global
...
13 matches
Mail list logo
