Health Check Endpoint Warnings (MS8) #2583
Unanswered
tmberthold
asked this question in
Q&A
Replies: 1 comment 6 replies
-
The idea was to define 4 clear api contexts, as stated in this decision record. I'd say that in fact for most of the cases would be preferred to have the health check exposed on a different api context (like the If we want to do this upstream let's wait for more opinions, then an issue/PR would be appreciated. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
We want to use health checks in our docker containers.
Currently there are two healthcheck endpoints, we are using the endpoint under the management context as suggested by the warning introduced in PR [1]. However we are currently getting a warning every 5 seconds about an outdated health URL..
Which is the correct health endpoint? If its under the mangegement API, why is it under the management API?
Endpoints under the management API might be secured by different means, which might make the management API unsuitable for Docker health check endpoints.
We are not using the default ports and paths:
http://localhost:11004/api/v1/management/check/health
(health check in management-context)http://localhost:8181/api/check/health
(health check in web-context)Both endpoints keep printing the same warning message:
The check/* endpoint has been moved under the 'management' context, please update your url accordingly, because this endpoint will be deleted in the next releases
[1] https://github.com/eclipse-edc/Connector/pull/2217/files
Beta Was this translation helpful? Give feedback.
All reactions