Skip to main content
Version: 5.4

Health Endpoints

The OPC router provides health endpoints that can be used to query data about the status of the OPC router, e.g. the redundancy state. Both the Runtime and the Web Management provide health endpoints.

note

The possible values for a status are:

  • Healthy
  • Unhealthy
  • Degraded

Health endpoints of the Web Management

The Web Management provides the following health endpoints.

EndpointDescription
/healthGeneral state of the Web Management
/health/liveLiveness probe
/health/readyReadiness probe
/health/detailsDetails on the status in JSON format
/health/runtime<Runtime health endpoint>Reverse proxy to the health endpoints of the Runtime

Health Endpoints of the Runtime

Configuration

The Heath endpoints of the Runtime can be configured using the following environment variables.

Environment variableDescriptionDefault value
OR_ENABLE_HEALTH_ENDPOINTActivates the provision of all health endpointstrue
OR_RUNTIME_HEALTH_ENDPOINT_PORTPort on which the Runtime provides the health endpoints53200
warning

The port configured with OR_RUNTIME_HEALTH_ENDPOINT_PORT is only accessible from localhost, e.g. from the Docker container or the Windows server in/on which the OPC router is running.

Endpoints

The Runtime provides the following health endpoints.

endpointdescription
/General state of the Runtime
/liveLiveliness probe
/ready

Readiness probe and general state of the Runtime

Returns the status code 200 if all health checks are successful.
Otherwise, the status code 503 is returned.

/detailsDetails of all health checks in JSON format
/RedundancyState

Current Redundancy state in JSON format e.g.

{"status": "Ready"}

The possible values for the redundancy status are:

  • Ready
  • Standby
  • LicenseError
/TransferManagerTransfer Manager health check
/RuntimeLicenseManagerLicense Manager health check
/HistoricalDiagnosisStorageCircular Storage health check
/TelemetryManagerTelemetry Manager health check