As these are on different ports to the engine api, so they also have own health like localhost:12700/actuator/health? Even if this hits same endpoint as engine health it could help when debugging potential connection/routing issues
There aren’t (just on the main url)
p.s. I don’t really have an opinion, but we could open a ticket and investigate how the spring actuator works with filters…
1 Like
I think it would be good to have a health check for each API, but I can live with using the engine health check, as I know the APIs are all in the same service in the same container
I’ve updated a pre-existing issue (we want to get rid of actuator, actually):