Skip to content
Arbitex Docs

Platform metrics

What it does

Section titled “What it does”

Platform metrics answers “is the service I pay for healthy, fast, and available?” with red/yellow/green (RYG) status across three axes: shared platform components (the gateway endpoint, DLP scan, and model routing — a service-level view, not internal pods), all deployment units where you’re deployed, and model-provider health. Raw infrastructure utilization (CPU/memory/disk) is an operator concern and isn’t shown here.

Configure in the UI

Section titled “Configure in the UI”
The Platform metrics panel showing an overall RYG status pill, a shared-components card grid with per-component status and latency, a deployment-unit health table, and a provider health table.
Monitoring & Reporting → Platform metricsCitadel synthetic data on a non-production Arbitex demo instance. Never client data.

  1. Open Monitoring & Reporting → Platform metrics. The Overall status pill at the top summarizes your account’s health.

  2. Review Shared components — one card per component with its RYG status, a detail line, and latency. If the platform’s per-component health read isn’t reachable, the section shows an explicit “temporarily unavailable” notice instead of a fabricated status.

  3. Review Deployment units — a healthy / degraded / offline summary plus a per-DU table (name, region, health, last seen, latency).

  4. Review Provider health — a per-provider table (status, detail, last checked), sourced from a live network probe.

  5. Latency figures render as “—” and availability-percent/uptime history are not shown yet — both are gated on a platform capability that hasn’t shipped; RYG status and current latency are live now.

API equivalent

Section titled “API equivalent”
Terminal window
curl -X POST "https://admin.arbitex.ai/api/v1/admin/monitoring/service-health/summary" \
  -H "Authorization: Bearer $ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

Plan & availability

Section titled “Plan & availability”

Available on every plan.

Deployment notes

Section titled “Deployment notes”

Deployment-unit RYG and provider health are read live from the platform data plane. In an air-gapped Hybrid Outpost with no path back to the Arbitex cloud, these sections degrade honestly to “temporarily unavailable” rather than showing stale or fabricated status.

Section titled “Related”