Документация VAS Experts en:dpi:epdg:monitoring

The alarm system

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:50:35+00:00

The alarm system Alarm categories Criticism Alarma

Architecture of the monitoring system

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:17:02+00:00

Architecture of the monitoring system Four-level monitoring architecture Level Component Technology Collection Built-in /metrics endpoint fast-epdg Prometheus text format over HTTP Storage Prometheus TSDB Local storage, 15-day storage by default

Components and indicators

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:19:31+00:00

Components and indicators Monitoring coverage Quantitative review by category Category Number of metrics Survey interval Key indicators Config

The deployment model

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T09:03:23+00:00

The deployment model Deployment characteristics Parameter Value Metrics footprint Integrated (~2 MB memory overhead) External dependencies

Integration into a single EPC Monitoring stack

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:54:54+00:00

Integration into a single EPC Monitoring stack ePDG monitoring is fully integrated into overall packet core monitoring: The NOC operator sees all EPC components (DPI, SMF, PCEF, FastPCRF, ePDG) in a single Grafana interface, with a single alarm system and notification routing through one Alertmanager.

Integration interfaces

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:29:42+00:00

Integration interfaces 1. Prometheus (CNCF Standard) The native /metrics endpoint on port 9817 is built into fast-epdg. The format is standard text format Prometheus v0.0.4 (compatible with OpenMetrics). Aggregation is supported with the central Prometheus operator; remote_write team support for long-term storage in Thanos, Cortex, Grafana Mimir.

List of metrics

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:24:21+00:00

List of metrics All metrics are exported through a single /metrics endpoint in Prometheus text format. The name follows the rules of Prometheus: epdg__[_unit], the Counter type has the suffix _total, Histogram is the suffix _seconds/_bytes

Coverage of metrics by OSI levels

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T09:00:31+00:00

Coverage of metrics by OSI levels Detailing metrics by level OSI model: Level Metrics Examples

Metric exporter configuration

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T09:04:59+00:00

Metric exporter configuration The monitoring section in fast-epdg.conf: monitoring { enabled = yes listen_port = 9817 listen_address = 0.0.0.0 update_interval = 10 metrics { ikev2 = yes gtp = yes diameter = yes service = yes session = yes app = yes system = yes } }

Standards and compatibility

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T09:01:46+00:00

Standards and compatibility Standard Area Application 3GPP TS 29.273 SWx/S6b/SWm Methodology for accounting for Diameter messages and resulting codes 3GPP TS 24.302 SWu (IKEv2) Definition of IKEv2 message types and error codes 3GPP TS 33.402

Visualization and operational dashboards

Anonymous (anonymous@undisclosed.example.com) — 2026-05-07T08:52:48+00:00

Visualization and operational dashboards Composition of dashboards Dashboard Panel Purpose ePDG Overview 10 Service availability, connection success rate, number of active sessions, SWu/SWm/S2b status, interface bandwidth IKEv2 Details 10