Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »


Introduction

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

Usage

This information can be used for normal system monitoring as well as for load balancing and high availability functions.

Health Check functions

The following functions can be called like normal HTTP GET Aufrufe calls:

Service

URL

Answer OK

Answer ERROR

What is being tested?

Description

CoreOne Authentication Service

https://${authenticationUrl}/health

HTTP 200

HTTP 500

HTTP 404

  • Database Connection

  • Application Service API

  • Discovery Document


CoreOne Authentication Service

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 Portal

https://${portalUrl}/health

HTTP 200

HTTP 500

HTTP 404

  • Authentication Service API

  • Application Service Health

CoreOne Portal

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

HTTP 200

HTTP 200 

HTTP 404

HTTP 500

  • Authentication Service API

  • Application Service Health

CoreOne Application Service

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

HTTP 200

HTTP 500

HTTP 404

  • Service is up and running (Implies Database Connectivity)


CoreOne Application Service API

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

HTTP 200

HTTP 500

HTTP 404

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

Detailed monitoring

The health checks listed above only provide information about whether the relevant Services are available, started and operational. The checks do not provide any information about internal processes, pending processes or the like.

This detailed information can also be monitored using managed services. Please get in touch with your contact person.

How-to articles

Filter by label

There are no items with the selected labels at this time.


  • No labels

© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.