Elastic-agent > nginx > logstash -- nginx proxy error

I need some logstash service to respond to the azure health-probe to be able to activate the application gatewai.

but it needs to be on the same protocol as the 5045 backend, which in this case is tcp/tls, do you have any ideas?

Not sure if I got your issue, but this is not related to Logstash.

I do not use Azure, but it seems that the Application Gateway supports TCP , so you need to create a health check using TCP.

Also, keep in mind that this will change how the agent communicate with Logstash, you will probably need to terminate the connection TSL connection on the Load Balancer in Azure and configure your logstash to listen without TLS.

I have a similar scenario on GCP, I have a SSL Network Load Balancer in front my Logstash, and this Load Balancer is terminating the TLS connection, Logstash is listening with ssl disabled.

The fleet manager in kibana, when configuring a logstash output in the fleet manager, it is mandatory to use a certificate. So whether I like it or not, my logstash has TLS enabled on TCP. I did the test using only TCP to see if logstash accepts it but it is really waiting for the certificate.

In Azure it works like this, I configure the backend port and protocol and the health probe uses the same protocol, giving me the option only to change the health probe port. And apparently the 9600 api listens on http, so I ran into a problem here, because the backend is TLS/TPC and the API is http/https