Back to corpus
research noteexperiment writeup candidatescore 32

ORB-2.1: Prometheus /metrics Endpoint

| Metric | Type | Description | |--------|------|-------------| | `orbit_project_count` | Gauge | Total registered projects | | `orbit_active_sessions` | Gauge | Active Claude sessions | | `orbit_websocket_connections` | Gauge | Connected WebSocket clients | | `orbit_api_requests_total` | Counter | API requests (labels: method, path, status) | | `orbit_query_latency_seconds` | Histogram | Query latency in seconds (label: operation) |

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Added a `/metrics` endpoint to the Orbit server exposing Prometheus text exposition format. ### Dependencies added - `metrics = "0.24"` (workspace) - `metrics-exporter-prometheus = "0.16"` with `http-listener` feature (workspace) ### Files changed - `Cargo.toml` — workspace dependency declarations - `crates/orbit-server/Cargo.toml` — server-level dependency references - `crates/orbit-server/src/metrics.rs` — **NEW** metrics module - `crates/orbit-server/src/main.rs` — wired module, AppState field, recorder init, route | Metric | Type | Description | |--------|------|-------------| | `orbit_project_count` | Gauge | Total registered projects | | `orbit_active_sessions` | Gauge | Active Claude sessions | | `orbit_websocket_connections` | Gauge | Connected WebSocket clients | | `orbit_api_requests_total` | Counter | API requests (labels: method, path, status) | | `orbit_query_latency_seconds` | Histogram | Query latency in seconds (label: operation) | ### Helper functions provided - `record_api_request(method, path, status)` — increment request counter - `record_query_latency(operation, start)` — record histogram observation

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.