What needs improvement with NGINX Plus?

The need for human involvement is high due to the complexity of NGINX's Linux-based terminology. More tactics and techniques can enhance its usability. Additionally, it is not a cost-effective solution for few applications. I would like the configuration process to be more simplified. Both Apache and NGINX involve some complex configuration steps. Easier configuration and troubleshooting would make it a perfect ten for me. … The solution must improve its performance. Sometimes, it could be because of how a customer has implemented the tool, but it is a potential bottleneck. The product must provide a holistic view of flows to help us understand the endpoints a particular transaction went through. The user interface could be improved. NGINX is also too poor with streaming. We could have a better solution for streaming besides NGINX. … The KPI on NGINX Plus should be more focused on load balancing and the latency in application calling from the end system. That is something currently lacking in the solution. I would also like to see a very interactive dashboard with all the KPI metrics that would help with application level troubleshooting. Finally, most people implementing this solution do not include a security model and it would be great if they could include that in the product. … I can’t speak to where the solution needs improvement. I’m just a user and I haven’t really gone in-depth in terms of looking for where the solution might have weak points. It would be great if there was even more automation to make it even easier to maintain. The center management system was not very good, maybe their new NGINX manager product is better. I'd like to see a good web management interface in the next release.