...
The following functions can be called like normal HTTP GET Aufrufe calls:
Service | URL | Answer OK | Answer FehlerhaftERROR | What is being tested? | Description |
---|---|---|---|---|---|
CoreOne Authentication Service | https://${authenticationUrl}/health | HTTP 200 | HTTP 500 HTTP 404 |
| |
CoreOne Authentication Service | https://${authenticationUrl}/health/details | HTTP 200 | HTTP 200 HTTP 404 HTTP 500 |
| Gives a 200 answer with a detailed list of which subsystems work and which do not. The 200 also appears when subsystems are not available. The content is intended for graphical assessment by system administrators. The 404 and 500 message appears if, for example, .NET Core hosting is missing on the system. |
CoreOne Web Service | https://${webUrl}/health | HTTP 200 | HTTP 500 HTTP 404 |
| |
CoreOne Web Service | https://${webUrl}/health/details | HTTP 200 | HTTP 200 HTTP 404 HTTP 500 |
| Gives a 200 answer with a detailed list of which subsystems work and which do not. The 200 also appears when subsystems are not available. The content is intended for graphical assessment by system administrators. The 404 and 500 message appears if, for example, .NET Core hosting is missing on the system. |
CoreOne Portal | https://${portalUrl}/health | HTTP 200 | HTTP 500 HTTP 404 |
| |
CoreOne Portal | https://${portalUrl}/health/details | HTTP 200 | HTTP 200 HTTP 404 HTTP 500 |
| |
CoreOne Application Service | http://${applicationUrl}:7000/health | HTTP 200 | HTTP 500 HTTP 404 |
...
The health checks listed above only provide information about wether whether the relevant Services are available, started and operational. The checks do not provide any information about internal processes, pending processes or the like.
...