Gateway Operational Endpoints

Purpose

This functional area exposes operational visibility from the ingress layer.

Main Capabilities

• health endpoints (liveness and readiness)
• metrics endpoints

Health Endpoints

The Gateway exposes its own health endpoints at the ingress layer:

• /health — overall gateway health
• /health/live — liveness probe, indicating the process is running
• /health/ready — readiness probe, indicating the gateway is ready to accept traffic

These endpoints are anonymous and covered by a dedicated rate limit policy to protect them from abuse while remaining accessible to monitoring systems.

Backend hosts expose their own health endpoints routed through the Gateway under /portal/health/... and /runtime/health/.... The Gateway probes these actively and adapts its routing if a backend becomes unhealthy.

Metrics Endpoint

The Gateway exposes a metrics endpoint for collection by monitoring infrastructure. This provides ingress-layer observability independently from backend service metrics.

Functional Value

This area lets operations teams observe gateway health separately from backend host health, and monitor the ingress layer as an independent component in the platform topology.