HAProxy is very weak in the logging and monitoring part and requires improvement. In the future, the tool should have additional modules for different purposes.
There is room for improvement in HAProxy's dynamic configuration. Currently, dynamic changes are lost when reloading the service, and it would be beneficial if dynamic configuration changes could be applied without losing the configuration or reloading the service, ensuring backups and preserving the static configuration.
The solution can be improved by controlling TCP behavior better rather than just reporting them in the logs. Automatic blocking of clients that don't properly close their TCP session (CH/CD) would be good.
Although HAProxy is essentially open-source, many features are not available. While troubleshooting, we are having some difficulties. There are no issues when it is running; it is stable and very good; however, if there is a troubleshooting issue or an incident occurs, we will have issues because this is open-source. We are only experiencing problems at that time. Otherwise, everything is fine. Because we need to search for a document or some troubleshooting information. That could be beneficial to us. To resolve the troubleshooting issues, additional documentation and troubleshooting are required. The product is satisfactory. However, additional documentation, additional technical documents, and troubleshooting steps are the types of things that can only make this solution better. Also, more clarity on where the package is hitting and where it is stopping is needed.
UNIX System Administrator at a financial services firm with 5,001-10,000 employees
Real User
2021-11-10T07:23:25Z
Nov 10, 2021
The logging is pretty hard to understand, but the documentation for the logging is decent. That would be my only criticism. Sometimes it's challenging to get through the log, and you need a log to understand what is going on. It isn't easy to map the logging with the documentation, and every time I read the log, I have to pull out the documentation to understand what I'm reading. And there is some more functionality that I would like to see. For example, you'll do a TLS to the front leg— whatever connects to your load balancer. You do the HTBS or whatever TLS connection there. And then, on the back end, you usually have to clear it a lot of times. I want to be able to do TLS all the way through on both legs. I don't know if it can do that. HAProxy might be able to do this already, but I haven't done enough research to see if this is possible
Director at a financial services firm with 501-1,000 employees
Real User
2021-07-23T09:21:59Z
Jul 23, 2021
There is no standardized document available. So, any individual has to work from scratch to work it out. If some standard deployment details are available, it would be helpful for people while deploying it. There should be more documentation on the standard deployment. When you have to customize it for your application requirements, there are a lot of challenges. There should be more support for customization. To customize it better, there should be some kind of programming integration.
UNIX System Administrator at a financial services firm with 5,001-10,000 employees
Real User
2019-06-04T07:43:00Z
Jun 4, 2019
The logging functionality could use improvement, as it is a little cryptic. Additional logging functionality with better documentation would be helpful.
HAProxy is considered by many in the industry to be one of the fastest and most popular and trusted software load balancer products in the marketplace today. Organizations are able to immediately deploy HAProxy solutions to enable websites and applications to optimize performance, security, and observability. HAProxy solutions are available to scale to any environment.
HAProxy is an open-source product and has a robust, active, reliable community. The solutions are continually tested and...
The solution's implementation and troubleshooting are not easy. The solution's dashboards and reports could be improved.
The product has the basic foundations of any load-balancing product. It is simple and basic. The product does not have any new technologies.
HAProxy is very weak in the logging and monitoring part and requires improvement. In the future, the tool should have additional modules for different purposes.
There is room for improvement in HAProxy's dynamic configuration. Currently, dynamic changes are lost when reloading the service, and it would be beneficial if dynamic configuration changes could be applied without losing the configuration or reloading the service, ensuring backups and preserving the static configuration.
There is room for improvement in the pricing model. It could be cheaper.
The visibility could be improved. Stability can falter when there is a lot of traffic. End-to-end connections are limited.
The solution has bad performance issues.
The solution can be improved by controlling TCP behavior better rather than just reporting them in the logs. Automatic blocking of clients that don't properly close their TCP session (CH/CD) would be good.
I would like to see better search handling, and a user interface, with a complete functional graphical unit.
HAProxy could do with some good combination integrations.
Although HAProxy is essentially open-source, many features are not available. While troubleshooting, we are having some difficulties. There are no issues when it is running; it is stable and very good; however, if there is a troubleshooting issue or an incident occurs, we will have issues because this is open-source. We are only experiencing problems at that time. Otherwise, everything is fine. Because we need to search for a document or some troubleshooting information. That could be beneficial to us. To resolve the troubleshooting issues, additional documentation and troubleshooting are required. The product is satisfactory. However, additional documentation, additional technical documents, and troubleshooting steps are the types of things that can only make this solution better. Also, more clarity on where the package is hitting and where it is stopping is needed.
We've changed solutions as it doesn't fit with our current needs.
The logging is pretty hard to understand, but the documentation for the logging is decent. That would be my only criticism. Sometimes it's challenging to get through the log, and you need a log to understand what is going on. It isn't easy to map the logging with the documentation, and every time I read the log, I have to pull out the documentation to understand what I'm reading. And there is some more functionality that I would like to see. For example, you'll do a TLS to the front leg— whatever connects to your load balancer. You do the HTBS or whatever TLS connection there. And then, on the back end, you usually have to clear it a lot of times. I want to be able to do TLS all the way through on both legs. I don't know if it can do that. HAProxy might be able to do this already, but I haven't done enough research to see if this is possible
There is no standardized document available. So, any individual has to work from scratch to work it out. If some standard deployment details are available, it would be helpful for people while deploying it. There should be more documentation on the standard deployment. When you have to customize it for your application requirements, there are a lot of challenges. There should be more support for customization. To customize it better, there should be some kind of programming integration.
Pricing, monitoring, and reports can be improved.
The logging functionality could use improvement, as it is a little cryptic. Additional logging functionality with better documentation would be helpful.