I know that haproxy exposes metrics like „Tr“ and “Tt”. My problem with the
application I have to proxy is that this application hides all of her
functionality behind one endpoint. To address the app I have to POST to (just
an example) https://hpalm/endpoint.
The payload that gets POSTed
I`m having problems with running haproxy 1.8 on CentOS 7.4 and originally I
planned to post my setup, logs and more. But while thinking about this I
started to doubt that what I am trying is correct.
Let me explain what I'm doing, perhaps there is a better approach which solves
my problem
I need to set up haproxy 1.8.3 as a loadbalancer for several nginx webservers
(1.13.x). The haproxy will be set up to support h2 connections.
I am undecided if it is a good idea to setup nginx for h2 also. I understand
that haproxy will be able to talk to nginx more efficiently, but there is
I thought about simplifying my haproxy configurations. I will end up with
several servers running similar setups. The idea is to split the single
"haproxy.cfg" into several files and combining common parts into separate files
and adding differential config files where appropriate.
Running
4 matches
Mail list logo