The document provides an overview of the Zabbix monitoring platform. It discusses why monitoring is needed, compares Zabbix to other monitoring tools like Nagios, Prometheus, and PRTG, and describes Zabbix's features including data gathering, alerting, graphing, templates, and architecture. The document also covers Zabbix agents, proxies, notifications, and common use cases for server and service monitoring.

1. Zabbix Monitoring
Platform
Presented By Majid Ettehadi
@ Mashhad LUG
1 Aug 2018

2. 2
Content
●
Why we need monitoring?
●
Why we choose Zabbix?
●
Zabbix introduction
●
Zabbix features overview
●
Zabbix architecture overview
●
Zabbix notification
●
Use cases and solutions

3. 3
Monitoring
●
Cost of downtime is high
●
Hard to manage
nontransparent environment
●
Record state and events of
system (history)
●
Keep track of system
resources

4. 4
Monitoring Tools - Nagios Core
●
Free and open source
●
Run under Linux and other Unix variants
●
Monitoring supported through SSH or SSL encrypted
●
Available data graphing plugins
●
Have different agents for different types of monitoring
●
Monitoring and alerting:
– Network services (SMTP, POP3, HTTP, NNTP, ICMP, SNMP, FTP, SSH)
– Host resources (processor load, disk usage, system logs) on a
majority of network operating systems, including Microsoft Windows
– Any hardware (like probes for temperature, alarms, etc.) which have
the ability to send collected data via a network

5. 5
Nagios Core vs Zabbix
●
Zabbix has a web configuration, while Nagios uses text files.
●
Zabbix has graphs and stats collection via SNMP or custom
agent. Nagios don't.
●
Zabbix is resource hungry. It uses a data base to store all the
stats and configuration and this can grow exponentially
depending on the number of hosts you are monitoring. Nagios
works very fast and normally will not require the ammount of
resources
●
Once the Zabbix agent is installed , most of the resource
monitoring is automatically added (Minimum configuration
needed)
●
Zabbix has auto discovery
●
Zabbix has native JMX support

6. 6
Monitoring Tools - Prometheus (1)
●
Free and open source
●
Originally built at SoundCloud!
●
Have multi-dimensional data model with time series
data identified by metric name and key/value pairs
●
Have flexible query language to leverage this
dimensionality
●
Pushing time series is supported via an intermediary
gateway
●
Targets are discovered via service discovery or static
configuration
●
Multiple modes of graphing and dashboarding support

7. 7
Monitoring Tools - Prometheus (2)

8. 8
Prometheus vs Zabbix

9. 9
Monitoring Tools – PRTG (1)
●
Not available in Iran!
●
Free version is very limited (only 100 Sensors)!
●
Monitor network, servers, websites and applications
●
PRTG can scan network segments by pinging
defined IP ranges. This way PRTG will automatically
recognize a wide range of devices and systems and
create sensors from predefined device templates.
●
Bandwidth monitoring (SNMP and WMI, Packet
Sniffing, NetFlow, IPFIX, jFlow, and sFlow)

10. 10
Monitoring Tools – PRTG (2)

11. 11
PRTG vs Zabbix
●
PRTG has better automatic network and
device discovery
●
PRTG has better GUI/Web intuitive
interface
●
PRTG has network and topology maps
●
PRTG has bandwidth and netflow
analysis (sFlow, jFlow, IPFix, etc)
●
PRTG has native mobile App

12. 12
Monitoring Tools - Other
●
SolarWinds
●
Spiceworks
●
Netrdata
●
Icinga
●
LinreNMS
●
You tell me!

13. 13
Zabbix
●
NAME: ZABBIX SIA
●
FOUNDER,OWNER & CEO: Alexei Vladishev
●
ESTABLISHED In 2005
●
STRUCTURE
– Zabbix SIA is a limited liability company registered in the Republic of Latvia
– SUBSIDARIES: Zabbix Japan LLC – registered in Japan, 100% of belongs to
Zabbix SIA
●
MISSION: To create top-quality open source monitoring platform of
choice for solving real needs of users backed by the excellent level of
commercial services
●
STRATEGY:
– Stay Open Source
– Concentrate on enterprise-level companies, while continue to be the best
solution for small and medium Companies

14. 14
Supported Platforms
●
Linux
●
IBM AIX
●
FreeBSD
●
NetBSD
●
OpenBSD
●
HP-UX
●
Mac OS X
●
Solaris
●
Windows: all desktop and server versions since 2000
(Zabbix agent only)

15. 15
Zabbix Features (1)
●
Data gathering
– Availability and performance checks
– Support for SNMP (both trapping and polling), IPMI, JMX, VMware monitoring
– Custom checks
– Gathering desired data at custom intervals
– Performed by server/proxy and by agents
●
Flexible threshold definitions
– You can define very flexible problem thresholds, called triggers, referencing
values from the backend database
●
Highly configurable alerting
– Sending notifications can be customized for the escalation schedule, recipient,
media type
– Notifications can be made meaningful and helpful using macro variables
– Automatic actions include remote commands

16. 16
Zabbix Features (2)
●
Real-time graphing
– Monitored items are immediately graphed using the built-in
graphing functionality
●
Web monitoring capabilities
– Zabbix can follow a path of simulated mouse clicks on a web site
and check for functionality and response time
●
Extensive visualisation options
– Ability to create custom graphs that can combine multiple items
into a single view
– Custom screens and slide shows for a dashboard-style overview
– Reports
– High-level (business) view of monitored resources

17. 17
Zabbix Features (3)
●
Historical data storage
– Data stored in a database
– Configurable history
– Built-in housekeeping procedure
●
Easy configuration
– Add monitored devices as hosts
– Hosts are picked up for monitoring, once in the database
– Apply templates to monitored devices
●
Use of templates
– Grouping checks in templates
– Templates can inherit other templates

18. 18
Zabbix Features (4)
●
Network discovery
– Automatic discovery of network devices
– Agent auto registration
– Discovery of file systems, network interfaces and SNMP OIDs
●
Fast web interface
– A web-based frontend in PHP
– Accessible from anywhere
– You can click your way through
●
Zabbix API
– Zabbix API provides programmable interface to Zabbix for mass
manipulations, 3rd party software integration and other purposes.

19. 19
Zabbix Features (5)
●
Permissions system
– Secure user authentication
– Certain users can be limited to certain views
●
Full featured and easily extensible agent
– Deployed on monitoring targets
– Can be deployed on both Linux and Windows
●
Binary daemons
– Written in C, for performance and small memory footprint
– Easily portable
●
Ready for complex environments
– Remote monitoring made easy by using a Zabbix proxy

20. 20
Zabbix Architecture (1)
●
Server
– Zabbix server is the central component to which agents report availability and
integrity information and statistics. The server is the central repository in
which all configuration, statistical and operational data are stored.
– Written by C
●
Database storage
– All configuration information as well as the data gathered by Zabbix is stored
in a database.
– Supoorts: MySQL, Oracle, PostgreSQL, SQLite, IBM DB2
●
Web interface
– For an easy access to Zabbix from anywhere and from any platform, the web-
based interface is provided. The interface is part of Zabbix server, and usually
(but not necessarily) runs on the same physical machine as the one running
the server.
– Written by PHP

21. 21
Zabbix Architecture (2)
●
Proxy
– Zabbix proxy can collect performance and availability data on behalf of Zabbix
server. A proxy is an optional part of Zabbix deployment; however, it may be very
beneficial to distribute the load of a single Zabbix server.
●
Agent
– Zabbix agents are deployed on monitoring targets to actively monitor local
resources and applications and report the gathered data to Zabbix server.
●
Data flow
– In addition it is important to take a step back and have a look at the overall data
flow within Zabbix. In order to create an item that gathers data you must first create
a host. Moving to the other end of the Zabbix spectrum you must first have an item
to create a trigger. You must have a trigger to create an action. Thus if you want to
receive an alert that your CPU load it too high on Server X you must first create a
host entry for Server X followed by an item for monitoring its CPU, then a trigger
which activates if the CPU is too high, followed by an action which sends you an
email. While that may seem like a lot of steps, with the use of templating it really
isn't. However, due to this design it is possible to create a very flexible setup.

22. 22
Zabbix agent modes

23. 23
Notifications & Automatic actions
●
Delivery methods
– by e-mail, by SMS, by Jabber, by Ez texting
and using a custom alertsript

24. 24
Zabbix use cases
●
Monitor server resources
– CPU, Memory, Swap, Disk, Network
●
Monitor services
– NTP, Network, HTTP, FTP, MySQL, …
●
Web Monitoring
– By Web scenarios
– Check Availablity, Responce Time, etc of a Website
●
Monitor Applications
– Containers, Custom scripts, ...
●
Monitor hardwares and network nodes

25. 25
Thank You