ProfessionalObservability engineering
Automated Zabbix monitoring for Azure network services and private VMs
Python collectors that bring ExpressRoute, VPN and Traffic Manager metrics from Azure Monitor into Zabbix, plus a zero-touch agent rollout that works on internet-facing and isolated private networks alike.
- Role
- Designer and implementer
- Context
- ALIANDO · Managed Services area
- Period
- 2025
01Overview
Network services are where outages start and where they are hardest to see. I automated the onboarding of Azure ExpressRoute, VPN connections and Traffic Manager into Zabbix, and built a zero-touch way to install Zabbix agents on VMs — including those in isolated private networks.
02Context
Client environments in ALIANDO’s Managed Services area are monitored centrally with Zabbix. Azure’s managed network services expose their health through Azure Monitor rather than through an agent, and many VMs sit in private networks without internet access.
03Problem statement
Configuring monitoring for each circuit, connection and profile by hand is slow and inconsistent, and a monitoring gap on a network service means degradations are found by users. Installing agents manually over RDP does not scale and is not always possible on isolated networks.
04My responsibilities
- Automated the onboarding of ExpressRoute, VPN connection and Traffic Manager monitoring into Zabbix.
- Built Python collectors that read Azure Monitor metrics for these services.
- Engineered a zero-touch Zabbix agent installation workflow using Azure CLI and Blob Storage.
05Architecture overview
Two complementary paths. For managed network services, Python collectors query the Azure Monitor metrics API — ExpressRoute ingress/egress bandwidth, BGP and ARP availability and circuit health; Traffic Manager endpoint health, queries per second and routing configuration — and feed them into Zabbix. For virtual machines, Azure CLI Run Command executes an installation script on the VM, which retrieves the agent package from Blob Storage; no RDP session or interactive credentials are required, and the approach works in isolated private networks.
- Azure service
- Observability
- Code & configuration
- Delivery & automation
- Platform / runtime
- Data & storage
Text description of the diagram
ExpressRoute circuits, VPN connections and Traffic Manager profiles publish platform metrics to Azure Monitor; Python collectors query the metrics API and send the values to the Zabbix server. Separately, Azure CLI Run Command executes an installer on a Windows VM, which downloads the agent package from Blob Storage; the installed Zabbix agent registers with the Zabbix server.
Flows
- ExpressRoute → Azure Monitor (platform metrics)
- VPN → Azure Monitor
- Traffic Manager → Azure Monitor
- Azure Monitor → Python collectors (query)
- Python collectors → Zabbix server (values)
- Azure CLI → Windows VM (script)
- Blob Storage → Windows VM (download)
- Windows VM → Zabbix agent (installs)
- Zabbix agent → Zabbix server (registers)
Components
ExpressRoute · VPN · Traffic Manager · Azure Monitor · Python collectors · Zabbix server · Azure CLI · Windows VM · Blob Storage · Zabbix agent
06Technology stack
- Sources
- ExpressRoute
- VPN Gateway connections
- Traffic Manager
- Collection
- Azure Monitor metrics API
- Python
- Agent rollout
- Azure CLI Run Command
- PowerShell
- Blob Storage
- Monitoring
- Zabbix server
- Zabbix agent
07Implementation approach
- ExpressRoute: ingress and egress bandwidth, utilisation, BGP and ARP availability and circuit health brought into Zabbix.
- Traffic Manager: endpoint health, queries per second and routing configuration collected from Azure Monitor.
- VPN connections onboarded with the same pattern, so all three services alert consistently.
- Agent installation driven by Azure CLI Run Command and a PowerShell installer — no RDP session and no interactive credentials on the VM.
- Agent package served from Blob Storage so that VMs without internet access can still be provisioned.
08Challenges & engineering decisions
Challenge
Managed network services cannot run a monitoring agent.
Decision
Collect their metrics from the Azure Monitor API and translate them into Zabbix, so they sit next to the rest of the estate in the same alerting model.
Challenge
VMs in isolated private networks cannot download installers from the internet, and RDP access is not always available.
Decision
Use Azure Run Command to execute the installer through the Azure control plane and host the package in Blob Storage reachable from the VM.
09Security considerations
- Run Command executes through Azure RBAC on the control plane, avoiding open RDP access and shared interactive credentials.
- Monitoring reads platform metrics only; collectors need read access to metrics, not management rights over the network resources.
10Operational considerations
- Consistent alerting across ExpressRoute, VPN and Traffic Manager.
- Proactive detection of resource degradation before users report it.
- Less configuration effort per new circuit, connection, profile or VM.
11Results & impact
- Automated monitoring onboarding for ExpressRoute, VPN connections and Traffic Manager.
- Improved reliability through proactive detection of degradation.
- Agent provisioning that works on both internet-facing and isolated private networks.
12Lessons learned
- Managed services need a metrics-API path into monitoring; agents only cover what you host.
- Designing for the most restricted network first produces a rollout that works everywhere.