OmniAUSF Metrics
Metrics are exposed at http://{host}:{prometheus_metrics_port}/metrics (default port 9568).
AUSF Metrics
| Metric | Type | Labels | Description |
|---|---|---|---|
omni_ausf_auth_count | counter | result | UE authentication operations. result is one of initiated (vector obtained, challenge returned), success (RES* matched XRES*), failure (UDM error, malformed vector, or RES* mismatch), resync (an AUTS/SQN resynchronisation was detected and relayed to the UDM), or resync_invalid (a malformed resync blob was dropped) |
omni_ausf_nrf_registration_status | gauge | nf_type | NRF registration status (1 = registered, 0 = not registered) |
omni_ausf_active_contexts_count | gauge | - | Number of active UE authentication contexts. Live gauge driven by the telemetry event [:omniausf, :ue_contexts, :active], emitted on every context create and delete and on each ContextReaper sweep, so it tracks the current in-flight context count |
omni_ausf_active_contexts_countis a live gauge. It is driven by the telemetry event[:omniausf, :ue_contexts, :active], which the AUSF context store emits whenever the set of active contexts changes: on context create, on delete (confirmation, deregister, or authentication-result delete), and on each ContextReaper sweep that reaps idle contexts. The gauge therefore mirrors the current active auth-context count and is safe to alert on and dashboard. The OAM API remains available for cross-checks:GET /api/status/nf(includes an active UE context count) orGET /api/statistics(total / success / failure / pending session counters).
omni_ausf_auth_countcovers the primary authentication flow plus the resynchronisation path. Theresyncandresync_invalidlabels count SQN resynchronisation attempts detected on the initiation request (validated-and-relayed, and malformed-and-dropped, respectively). The deregister and authentication-result-delete paths emit their own telemetry events but are not currently attached to any exported Prometheus metric.
Internal telemetry (not a Prometheus metric). The context reaper emits a
[:omniausf, :ausf, :context_reap]telemetry event carrying the count of contexts reaped per sweep. This is internal telemetry for operators wiring their own handlers; it is not registered as an exported Prometheus metric.
Example PromQL
-
Authentication success rate over 5 minutes:
sum(rate(omni_ausf_auth_count{result="success"}[5m])) / sum(rate(omni_ausf_auth_count{result="initiated"}[5m])) -
Authentication failures per second:
sum(rate(omni_ausf_auth_count{result="failure"}[5m])) -
AUSF currently registered with the NRF:
omni_ausf_nrf_registration_status == 1 -
SQN resynchronisation attempts per second (valid vs malformed):
sum(rate(omni_ausf_auth_count{result="resync"}[5m]))andsum(rate(omni_ausf_auth_count{result="resync_invalid"}[5m])) -
Active in-flight authentication contexts:
omni_ausf_active_contexts_count
For an independent cross-check of the in-flight context count, the OAM API (GET /api/status/nf or GET /api/statistics) reports the same figure.
BEAM VM Metrics
| Metric | Type | Description |
|---|---|---|
beam_memory_total | gauge | Total BEAM memory in bytes |
beam_memory_processes | gauge | Memory used by Erlang processes |
beam_memory_system | gauge | System memory (ETS, atoms, code) |
beam_processes_count | gauge | Number of Erlang processes |
beam_vm_uptime | gauge | VM uptime in seconds |