Skip to content

Azure || Move Health check to a different port

Krishna Nikhil Vedurumudi requested to merge health into master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

  • [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

The Spring Actuator endpoint is currently not used. Under load, if all the threads in Tomcat threadpool become busy, the containers do not respond back to health checks on time and end up being dropped off from the App Gateway.

What is the new/expected behavior?

Moved SpringBoot Actuator endpoint to a separate port - This support comes by default with Spring which can be turned on by toggling an additional property.

Have you added/updated Unit Tests and Integration Tests?


Any other useful information

Container availability and Healthy host count before and after change.





Edited by Krishna Nikhil Vedurumudi

Merge request reports