Apiserver is the main interactive entry point into the hub. Browser sessions, API clients, and exporter control-plane requests reach the hub through this service, so it is responsible for authentication, authorization, request handling, and serving the UI.Most user workflows combine metadata with telemetry. Apiserver reads and writes metadata in PostgreSQL, such as users, roles, dashboards, alerts, environments, and integration configuration. When a user opens a telemetry view or an API client asks for observability data, Apiserver queries ClickHouse and returns the results in the shape the UI or API expects.Longer-running work is handed to Temporal instead of being kept inside a request handler. This lets Apiserver start workflow-backed features without making user requests wait for every background step to finish.
Apiserver is stateless and is designed to run as multiple replicas behind the ingress path. It can be scaled horizontally as UI and API traffic grows. It does not own durable state locally; PostgreSQL, ClickHouse, and Temporal are the services that determine whether most API workflows can complete successfully.Operators should treat Apiserver health as a signal for the control plane and UI path. If Apiserver is healthy but user queries are slow, the next places to inspect are usually ClickHouse query performance, PostgreSQL metadata access, or Temporal workflow health depending on the affected feature.
