You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this should be a feature request for this project or the spring boot actuator project since the elasticsearch indicator is provided by that project. Raising here since the spring-data-elasticsearch project is a spring project, whereas spring-data-opensearch is not, hopefully this is the right place!
Is your feature request related to a problem?
If our application is unable to connect to opensearch then we can see lots of errors in the logs such as
however the application does start up and the /actuator/health endpoint shows that all is healthy status is UP. This is incorrect since the application is certainly not healthy if it can't connect to opensearch.
What solution would you like?
It would therefore be good to have a health indicator that is automatically included to indicate whether we can connect to opensearch. Note that the elasticsearch health indicator actually calls the /_cluster/health endpoint, which goes beyond checking whether we can connect to the cluster and actually lets us know the state of the cluster. If this is a relatively cheap operation then this sounds fine, otherwise some sort of ping would normally be preferable.
What alternatives have you considered?
We could write our own health indicator, but it feels like there should be something out of the box.
The text was updated successfully, but these errors were encountered:
I'm not sure if this should be a feature request for this project or the spring boot actuator project since the elasticsearch indicator is provided by that project. Raising here since the spring-data-elasticsearch project is a spring project, whereas spring-data-opensearch is not, hopefully this is the right place!
Is your feature request related to a problem?
If our application is unable to connect to opensearch then we can see lots of errors in the logs such as
however the application does start up and the
/actuator/health
endpoint shows that all is healthystatus
isUP
. This is incorrect since the application is certainly not healthy if it can't connect to opensearch.What solution would you like?
It would therefore be good to have a health indicator that is automatically included to indicate whether we can connect to opensearch. Note that the elasticsearch health indicator actually calls the
/_cluster/health
endpoint, which goes beyond checking whether we can connect to the cluster and actually lets us know the state of the cluster. If this is a relatively cheap operation then this sounds fine, otherwise some sort ofping
would normally be preferable.What alternatives have you considered?
We could write our own health indicator, but it feels like there should be something out of the box.
The text was updated successfully, but these errors were encountered: