Case study
Network Monitoring System (Telecom)
Led design and implementation of a distributed NMS spanning 1000+ nodes, with Angular dashboards, ASP.NET Core microservices on Kubernetes, Kafka, Prometheus, and Zabbix.
- Role
- Technical Lead
- Published
- Tags
- telecom · monitoring · microservices · kafka · reliability
Managed nodes
1000+
Nationwide network monitoring scope
Downtime reduction
-30%
Improved operational visibility and response speed
Engineering team
15
Cross-functional monitoring and platform delivery
Problem
Monitoring large-scale telecom infrastructure was fragmented and slow. Operations teams lacked a unified, real-time view across network nodes, which made incidents harder to prioritize and increased the time needed to understand impact.
Solution
I led the design and implementation of a distributed monitoring system built as ASP.NET Core microservices deployed on Kubernetes, with PostgreSQL for operational data where relational queries helped reporting and configuration flows. Kafka carried telemetry events, Prometheus and Zabbix covered metrics and infrastructure monitoring, and Angular delivered real-time dashboards and alerting views for operators.
Architecture decisions
- Kubernetes packaged microservices for repeatable rollout and horizontal scaling as the monitored estate grew.
- Distributed collectors reduced pressure on central services and allowed monitoring to continue closer to the network edge.
- Kafka decoupled ingestion from dashboard processing so spikes in telemetry would not directly block the operator experience.
- Prometheus and Zabbix were integrated for complementary monitoring, alerting, and infrastructure visibility alongside Angular operator UIs.
Impact
- Reduced downtime by 30% through faster detection and response.
- Enabled real-time monitoring across 1000+ nodes.
- Gave operations teams a clearer system view instead of fragmented monitoring paths.