Module metrics 

HTTP-core verdict-edge metrics surfaced through the workspace chio-metrics-spec registry. The HTTP edge is wired into the workspace registry: every authority dispatch through HttpAuthority::evaluate increments CHIO_GUARD_EVALUATIONS_TOTAL with a (guard, outcome) label pair and observes the dispatch latency under CHIO_KERNEL_DECISION_LATENCY_SECONDS.

Constants

CHIO_GUARD_EVALUATIONS_TOTAL

CHIO_KERNEL_DECISION_LATENCY_SECONDS

DECISION_LATENCY_BUCKETS_SECONDS

GUARD_LABEL_HTTP_AUTHORITY

GUARD_OUTCOME_ALLOW

GUARD_OUTCOME_DENY

GUARD_OUTCOME_ERROR

Functions

decision_latency_count

guard_evaluations_total

observe_decision_latency_nanos

Observe a kernel decision latency sample in nanoseconds.

observe_decision_latency_nanos_for_outcome

Observe a kernel decision latency sample in nanoseconds for a verdict outcome. Unknown labels fail closed into the error series.

record_dispatch_failure

+1 on chio_dispatch_failure_total for a genuine mediation-edge failure: the request could not be evaluated (a fail-open/dispatch condition). outcome is “error”. A normal policy/capability deny is an expected fail-closed decision, NOT a dispatch failure, and must never feed this counter or it would page the P0 alert on every rejected request. Denies are tracked by the guard-verdict metrics instead. Never called on allow.

record_guard_evaluation

Record the outcome of an HTTP authority evaluation. The outcome argument should be one of GUARD_OUTCOME_ALLOW, GUARD_OUTCOME_DENY, or GUARD_OUTCOME_ERROR.

render_http_core_metrics_prometheus