{"id":42551,"date":"2019-04-18T07:41:32","date_gmt":"2019-04-18T05:41:32","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=42551"},"modified":"2019-04-18T07:41:41","modified_gmt":"2019-04-18T05:41:41","slug":"zabbix-in-the-munich-subway","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2019\/04\/18\/zabbix-in-the-munich-subway\/","title":{"rendered":"Zabbix in the Munich subway"},"content":{"rendered":"\n\n
\"\"<\/figure>\n\n\n\n

Zabbix blog<\/a> shares a very inspiring post “Zabbix in the subway. Munich Transport Corporation Case Study<\/a>“, which shows how Zabbix<\/a> is used for the monitoring of the trains and trams in Munich. Here are some implementation details to get you started:<\/p>\n\n\n\n

Currently, there are 3796 devices monitored by the Zabbix server, which in turn houses the MySQL database and the web front-end. This server is operated virtually with 8 CPU\u2019s and 32GB RAM supported by SAS storage system. 105818 items are queried by the Zabbix server from those devices, where 23820 triggers detect whether certain items deviate from their target state. This results in 298.48 NVPS with an average of approx. 7 people (actively) using the system concurrently. General overview:
* Each device inside a tram\/subway is treated as a host and is monitored for availability.
* Each tram\/subway is managed as a host group.
* Host groups are nested and organized by the tram\/subway lines (using the host group nesting feature introduced in Zabbix 3.2).
* All devices depend on the connectivity of the MRCU (Mobile Radio Control Unit in subways) or LTE router (LTE G4 Connectivity in trams)
* Maps are automatically created for each tram\/subway (using the Zabbix API).
* Maps use sub-maps to link to a specific tram\/subway view.<\/p><\/blockquote>\n\n\n\n

There’s also a video<\/a> from the Zabbix conference, presenting the case study.<\/p>\n\n\n\n

\n