Versions Compared

Old Version 15

changes.mady.by.user Victor Zebert (Unlicensed)

Saved on

compared with

New Version 16

changes.mady.by.user Marc Burkhard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This article describes how the servicesof the CoreOne Suite services can be monitored.

Usage

This information can be used for normal system monitoring as well as for load balancing and high availability functions. This should help our customers who would like monitor by theirself the application. Please do not forget to duplicate the monitoring system on all nodes if the application is deployed in a high availability deployment scenario. This System monitoring recommendations is not including a rudimentary server monitoring like cpuCPU, ram RAM or disk usage. This is of course also recommended.

...

Service

URL

Answer OK

Answer ERROR

What is being tested?

Description

CoreOne Authentication ServiceServices

https://${authenticationUrl}/health

HTTP 200

HTTP 500

HTTP 404

  • Database Connection

  • Application Service API

  • Discovery Document


CoreOne Authentication ServiceServices

https://${authenticationUrl}/health/details

HTTP 200


HTTP 200 

HTTP 404

HTTP 500


  • Database Connection

  • Application Service API

  • Internal Services

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

  • Application Service Health

  • Application Service API

  • Authentication Service Health


CoreOne Web Service

https://${webUrl}/health/details

HTTP 200

HTTP 200 

HTTP 404

HTTP 500

  • Application Service Health

  • Application Service API

  • Authentication Service Health

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 Self-Service Portal

https://${portalUrl}/health

HTTP 200

HTTP 500

HTTP 404

  • Authentication Service API

  • Application Service Health

CoreOne Self-Service Portal

https://${portalUrl}/health/details

HTTP 200

HTTP 200 

HTTP 404

HTTP 500

  • Authentication Service API

  • Application Service Health

CoreOne Application ServiceServices

https://${applicationUrl}:7000/health

HTTP 200

HTTP 500

HTTP 404

  • Service is up and running (Implies Database Connectivity)


CoreOne Application Service Services API

https://${applicationUrl}:8000/api/Health

HTTP 200

HTTP 500

HTTP 404

  • Validates the access token (Implies that the Authentication Servier is running)

...