Health checks of each component

Updated at:

SOFABoot supports health check functions for each component of the middleware. After the health check extension is added, you can directly access the http://localhost:8080/actuator/readiness in the browser to view the results of the Readiness Check of each component.

The following table describes how SOFABoot health check components.

Components

health check Content

Description

Result example

SOFARPC SOFAREST

Published and referenced services

Lists information about all published and referenced services. If the check passes, the status is UP. Otherwise, the status is DOWN.

  • "SOFABoot Modules":{"status": "UP","com.alipay.sofa.service-provider": "passed","com.alipay.sofa.service-consumer": "passed"}

DDCS

Whether the DDCS service address can be obtained from AntVip

If the drmdata service address can be obtained, the check is passed and the status is UP. Otherwise, the status is DOWN.

  • Check passed, print in log common-default.log: component readiness check success. component name[DDCS]

  • Check failed, print in log common-error.log: component readiness check failed. component name[DDCS]

Scheduler

Configuration check

Whether the configuration of app and instanceId is empty

  • Check passed, print in log common-default.log: component readiness check success. component name[SCHEDULER]

  • Check failed, print in log common-error.log: component readiness check failed. component name[SCHEDULER]

Long connection client check

Whether the client for a long connection is started successfully

Route service check

Whether the routing service is initialized successfully

MQ

client pub check

Whether the pub bean is started successfully

  • Check passed, print in log common-default.log: component readiness check success. component name[MQ]

  • Check failed, print in log common-error.log: component readiness check failed. component name[MQ]

Client sub check

Whether the sub bean is started successfully

DTX

Long connections from the client to the server

Whether the long connection from the client to the server is created successfully

  • Check passed, print in log common-default.log: component readiness check success. component name[dtx]; no retry.

  • Check failed, print in log common-error.log: component readiness check failed. component name[dtx]; no retry