Marcos Medina
Leer en español
All work

02/04 Monitoring × Infrastructure

Network Operations Platform

One operational picture of routers, IP telephony and PBXs, honest about how fresh every value is.

Role
Architecture & development
Context
Telecom infrastructure operations
Focus
Observability, data freshness, resilience
  • 5 Explicit data states, from live to degraded
  • 3 Device families: routers, IP telephony and PBX
  • Zabbix Monitoring integration

Interactive demo — Conceptual interface — not production screenshots

Fig. 02 Conceptual interface — not production screenshots

Overview

Telecommunications infrastructure is spread across very different devices: routers, IP phones, PBXs. Each speaks its own language and fails in its own way, and operators end up jumping between consoles to understand a single incident.

The platform brings that picture together. Monitoring data arrives through Zabbix, a Node.js/Express backend serves it to the interface, and the infrastructure is presented as an operational map rather than a list of hosts.

The challenge

Monitoring data is never perfectly fresh. Sources time out, polls lag behind, and a dashboard that shows a five-minute-old value as if it were current is worse than no dashboard at all: it builds false confidence.

The real challenge was to make the state of the data itself visible, so an operator can always tell “the device is fine” apart from “we don’t know right now”.

Architecture

Routers Edge & core IP telephony Phones & trunks PBX Call platforms Zabbix Monitoring source Node.js / Express Platform backend Data-state layer Freshness states Ops console One operational view Routers Edge & core IP telephony Phones & trunks PBX Call platforms Zabbix Monitoring source Node.js / Express Platform backend Data-state layer Freshness states Ops console One operational view
Hover or focus a component to trace its connections.

Key decisions

  1. 01

    An explicit data-state model

    Every piece of information carries one of five states: live, snapshot, stale, refreshing or degraded. The interface renders each differently, so freshness is never implicit.

  2. 02

    Zabbix as the monitoring backbone

    Rather than reinventing collection, the platform integrates with Zabbix and focuses on what operators need on top of it: context, grouping and clear status across device types.

  3. 03

    Degrade, don’t disappear

    When a source fails or answers partially, the last known information stays on screen, clearly marked as stale or degraded, instead of vanishing or pretending to be current.

  4. 04

    One backend, many device families

    A Node.js/Express backend gives routers, IP telephony and PBXs a common shape, so very different devices can be presented consistently in one interface.

Stack

  • Node.js
  • Express
  • Zabbix
  • Routers
  • IP telephony
  • PBX

Notes

The interfaces shown are conceptual mockups created for this portfolio. They are not production screenshots and contain no real infrastructure data.