Reporting Large Environment Zabbix Database

Reporting
Large Environment
Zabbix Database
2015 Sept

Alain Ganuchaud
Core IT Project
http://www.coreit.fr
alain@coreit.fr
Presentation
Page 2

Content
1. Reporting Components
2. Reporting Architecture for large
environment
3. Reports examples built with Jasper
Suite
Page 3

Summary
Part 1
Components
-> SQLs & Zabbix
Database Model
-> APIs
-> Jasper Suite
Part 2
Reporting
Architecture
-> Warehouse
Database
-> Reporting
Architecture
Part 3
Reports
-> Zabbix
Configuration
Checker
-> Manager
Dashboard
-> Yearly Trends
Page 4

Introduction
Page 5
-> What are we talking about ?
-> Large Environment
-> Problem
-> Example : Zabbix Configuration Checker

What are we talking about ?
Reporting
→ Extract essential Zabbix information to make
better decisions by viewing consolidated data
→ Presentation layer must be sexy
Data WareHouse
→ Consolidate Zabbix data with some enrichment
(teams, cmdb infos, …)
→ Read Only Database <> Zabbix Database
BI
→ retrieve, analyze, transform and report data
→ Jasper Suite (iReport & Jasper Server)
Page 6

What is a Large Environment ?
• More than 14 000 servers , 1 million
items
• Some servers with over 10 000 items
• Some servers with over 10 000 triggers
• More than 100 Zabbix administrators
developping Application Templates
Page 7

The Problem
In such huge environment, Zabbix (through the
frontend) gives back too much details and you
loose High level visibility (In French, we say « The
tree that hides the forest ».
Reporting can help in this area, unfortunately
Zabbix has no reporting facility.
→ You have to develop your own Reporting
Architecture to get a consolidated view on data.
Page 8

Example : Zabbix
Configuration Checker
• In the following slides, I will take the example of
Reports that are dispatched to the teams who are
responsible for an application.
• Those teams are in charge of Zabbix templates
development, as they are not Zabbix experts, they
do mistakes.
•Zabbix configuration Checker help those teams to
correct those templates by sending Reports about
bad or poor Zabbix Templates configurations.
Page 9

Part 1
Reporting Components
Page 10
-> Where is the information to report ?
-> Zabbix database schema
-> SQL vs API
-> BI : Jasper Suite

Where is the Information ?
In Zabbix Database
• Easy … select host from hosts where …
In Cache
• Glurps … APIs ?
→ Normally Reporting Data are meta data, we do
not care about details or data in cache !
Page 11

Zabbix Database schema
Page 12
Know
the
Database
schem
a
and
follow
the
changes

Page 13

Page 14

Page 15

Page 16
Nota Bene : No trend.get API

Page 17
Download Zabbix Database Model with comments at
https://share.zabbix.com/databases/mysql/zabbix-database-model
Versions 1.8 , 2.0 , 2.2 & 2.4

APIs
{
"jsonrpc": "2.0",
"method": "host.get",
"params": {
"output": "extend",
"filter": {
"host": [
"Zabbix server",
"Linux server"
]
}
},
"auth": "038e1d7b1735c6a5436ee9eae095879e",
"id": 1
}
Page 18
Ignore the Zabbix
Database schem
a …
som
e APIs are m
issing
ie trend.get

API vs SQL
Normally API requests are safe and are compatible with
Zabbix Database schema, but in Large environment they
are slow … for example triggers table size could be
about 1Gb.
That's why, most of the time I prefer SQL requests on a
Zabbix replicated Database, thus there no IOs generated
on Zabbix Production Platform.
It implies you know and follow Zabbix Database Schema
changes.
Page 19

Part 2
Reporting Architecture
Page 21
-> Monitoring Data WareHouse
-> iReport / JasperStudio
-> Jasper Server

Building DataWareHouse

Zabbix Configuration Checker
+-------------------------------------+
| Tables_in_zabbix_warehouse
+-------------------------------------+
| agent_unavailable
| bad_nomenclatures
| distrib_by_environment
| distrib_by_hostgroup
| distrib_by_os
| distrib_by_regularity
| distrib_by_status
| hosts_low_discovery_items
| hosts_low_discovery_triggers
| hosts_per_template
| hosts_with_not_templated_items
| hosts_with_numerous_events
| hosts_with_numerous_events_type_log
| hosts_with_old_triggers
| hosts_with_unsupported
| hosts_without_triggers
| items_log_without_skip_parameter
| teams
| templates_with_low_disc_regularity
| web_with_low_regularity
………………..
mysql> show create table distrib_by_regularity;
+----------------------------+----------------------------------------------
| Table | Create Table
+----------------------------+---------------------------------------------
distrib_by_regularity
CREATE TABLE `distrib_by_regularity` (
`team` varchar(64) COLLATE utf8_bin NOT NULL DEFAULT '',
`number` int(11) NOT NULL DEFAULT '0',
`regularity` int(11) NOT NULL DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin

$query_distrib_by_regularity = "select substring(i.name,5,3) as TEAM,
i.delay as REGULARITY, count(*) as NUMBER from items i INNER JOIN hosts h ON ( i.hostid = h.hostid ) where ….

Enrich DataWareHouse

iReport / JasperStudio

Subreports

Reports

Final Reporting Architecture

Part 3
Reports
Page 32
-> Zabbix Configuration Checker
-> Summary Report
-> Yearly Trends

Merci pour votre attention !
Alain Ganuchaud
Core IT Project
alain@coreit.fr
Questions?
Page 38
Follow us on Twitter: @zabbix_fr @AlainGanuchaud

Reporting Large Environment Zabbix Database

More Related Content

What's hot (20)

Similar to Reporting Large Environment Zabbix Database (20)

Recently uploaded (20)

Reporting Large Environment Zabbix Database