Zabbix certified specialist 7_Day_2_slides.pdf

guipamar365 13 views 160 slides Sep 16, 2025
Slide 1
Slide 1 of 160
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25
Slide 26
26
Slide 27
27
Slide 28
28
Slide 29
29
Slide 30
30
Slide 31
31
Slide 32
32
Slide 33
33
Slide 34
34
Slide 35
35
Slide 36
36
Slide 37
37
Slide 38
38
Slide 39
39
Slide 40
40
Slide 41
41
Slide 42
42
Slide 43
43
Slide 44
44
Slide 45
45
Slide 46
46
Slide 47
47
Slide 48
48
Slide 49
49
Slide 50
50
Slide 51
51
Slide 52
52
Slide 53
53
Slide 54
54
Slide 55
55
Slide 56
56
Slide 57
57
Slide 58
58
Slide 59
59
Slide 60
60
Slide 61
61
Slide 62
62
Slide 63
63
Slide 64
64
Slide 65
65
Slide 66
66
Slide 67
67
Slide 68
68
Slide 69
69
Slide 70
70
Slide 71
71
Slide 72
72
Slide 73
73
Slide 74
74
Slide 75
75
Slide 76
76
Slide 77
77
Slide 78
78
Slide 79
79
Slide 80
80
Slide 81
81
Slide 82
82
Slide 83
83
Slide 84
84
Slide 85
85
Slide 86
86
Slide 87
87
Slide 88
88
Slide 89
89
Slide 90
90
Slide 91
91
Slide 92
92
Slide 93
93
Slide 94
94
Slide 95
95
Slide 96
96
Slide 97
97
Slide 98
98
Slide 99
99
Slide 100
100
Slide 101
101
Slide 102
102
Slide 103
103
Slide 104
104
Slide 105
105
Slide 106
106
Slide 107
107
Slide 108
108
Slide 109
109
Slide 110
110
Slide 111
111
Slide 112
112
Slide 113
113
Slide 114
114
Slide 115
115
Slide 116
116
Slide 117
117
Slide 118
118
Slide 119
119
Slide 120
120
Slide 121
121
Slide 122
122
Slide 123
123
Slide 124
124
Slide 125
125
Slide 126
126
Slide 127
127
Slide 128
128
Slide 129
129
Slide 130
130
Slide 131
131
Slide 132
132
Slide 133
133
Slide 134
134
Slide 135
135
Slide 136
136
Slide 137
137
Slide 138
138
Slide 139
139
Slide 140
140
Slide 141
141
Slide 142
142
Slide 143
143
Slide 144
144
Slide 145
145
Slide 146
146
Slide 147
147
Slide 148
148
Slide 149
149
Slide 150
150
Slide 151
151
Slide 152
152
Slide 153
153
Slide 154
154
Slide 155
155
Slide 156
156
Slide 157
157
Slide 158
158
Slide 159
159
Slide 160
160

About This Presentation

Zabbix certified specialist

Size: 5.43 MB
Language: en
Added: Sep 16, 2025
Slides: 160 pages

Slide Content

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 2
Rules
Itisprohibitedtomakeanyvideoand/oraudiorecordingsduringthewholeperiodofthiscourse.
Thiscourseisintendedonlyfortheofficiallyenrolledstudent.SubjecttotheCopyrightNoticebelow,thestudentisnotallowedtoshare
theircredentialsforattendingthiscourse,toallowotherstojoinandtakepart,orotherwisemakeuseoftheseMaterials.
Copyrightnotice
©Zabbix,2025.Allrightsreserved.
Unlessotherwiseindicated,Zabbixownsthecopyrightandotherintellectualpropertyrightsinthetext,graphics,information,designs,
data,verbal/audio/videopresentationsandfiles,comments,drawings,examquestionsandexamanswers,andothertrainingcontent,lab
manualsandpracticaltasks,andtrainingcoursesthemselves(further–Materials).
TheMaterialsareprotectedbywatermarks,copyrightstatements,andothermeans.Itisprohibitedtoremoveanyofwatermarksand
copyrightstatements,orinanyotherwaytoamendorchangethecontentorappearanceoftheMaterials.
Anyunauthorizedreprint,publication,reproduction,sharing,oruseoftheMaterialsisprohibited.NopartoftheMaterialsmaybe
reproduced,transmitted,orpublishedinanyformorbyanymeans,electronicormechanical,includingphotocopying,recording,orby
anyinformationstorageandretrievalsystemwithouttheexpresssignedwrittenpermissionfromZabbix.
AllcourseMaterialsmadeavailabletothestudentduringthecourseofthetrainingmaybeusedsolelybythestudentenrolledinthe
relevantcourseforpersonalandeducationalpurposesonly.Materialsprovidedtothestudentshouldbetreatedasconfidential
informationsharedwiththestudentonlyforthepurposeofthestudentperformingZabbixCertifiedtraining.
Thestudentacknowledgesthatdamagesalonewouldnotbeanadequateremedyforthebreachofthiscopyrightandthestudentshall
beentitledtothegrantingofequitablereliefconcerninganythreatenedoractualbreachofanyoftheprovisionsofthisCopyrightnotice.
COPYRIGHT NOTICE [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 3
Zabbix agent
passive mode
Zabbix agent
active mode
UserParameters
Human readable data Update intervals Preprocessing
Triggers Trigger functions Problems [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 4
ZABBIX AGENT PASSIVE MODE
25 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 5
ZABBIX AGENT PASSIVE CHECKS
A Zabbix agent (passive) check is a simple data request:
Zabbix server or proxy sends a request to agent for a metric
Zabbix agent receives the request and sends back the result
SYSTEM.CPU.LOAD = ?
0.57
Zabbix agentZabbix server [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 6
AGENT POLLER PROCESS
Data from Zabbix passive agent is collected by the Agent pollerprocess:
This is an asynchronous data collector and can execute up to 1000 requests at once
Start more agent pollerson the server or proxies only if you have a lot of passive checks
Concurrent checks per pollercan be adjusted
### Option: StartAgentPollers
# Number of pre-forked instances of asynchronous Zabbix agent pollers.
# Mandatory: no
# Range: 0-1000
StartAgentPollers=1
### Option: MaxConcurrentChecksPerPoller
# Maximum number of asynchronous checks that can be executed at once by each
# HTTP agent poller, agent polleror SNMP poller
#
# Mandatory: no
# Range: 1-1000
MaxConcurrentChecksPerPoller=1000 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 7
SYNCHRONOUS VS ASYNCHRONOUS
Data collector
Network Network
1
1
2
2
3
3
1
2
3
4
5
1
4
3
6
2
7
Data collector
8
Synchronous data collection Asynchronous data collection [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 8
ZABBIX AGENT INTERFACE
Settings for connecting to a passive Zabbix agent are defined using interfaces:
Use a unique and descriptive host name
Create at least one agent interface and specify the IP address/DNS name of the target host
Specify the proxy server if the host will be monitored through a proxy
Zabbix agent
interface [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 9
HOST CONFIGURATION
To gather metrics using Zabbix agent passive check:
Create an item with type "Zabbix agent"
Specify a host interface of type "Agent"
Item type
Agent
interface
Agent interface
has its own
availability icon [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 10
SECURITY SETTINGS
Zabbix agent needs to be configured to accept requests from Zabbix server:
Adjust the "Server=" parameter in the Zabbix agent configuration file to match the Zabbix
server or proxy address
Multiple IP addresses, IP address ranges. or DNS names can be specified
Specifying 0.0.0.0/0 will accept a connection from any address (a very insecure setting!)
### Option: Server
# List of comma delimited IP addresses, or DNS names of Zabbix servers and Zabbix proxies.
# Incoming connections will be accepted only from the hosts listed here.
Server=192.168.0.5
SYSTEM.CPU.LOAD = ?
0.56
Server=192.168.0.5IP:192.168.0.5
I accept
connections
from 192.168.0.5 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 11
DROPPED AGENT CONNECTION
Agent will drop a connection if the address of server or proxy does not match:
Error will be logged in the Zabbix agent log file
Zabbix agent interface will become unavailable with a corresponding error message
2024/05/13 13:10:13.732776 failed to accept an incoming connection: connection from "192.168.0.5"
rejected, allowed hosts: "127.0.0.1"
SYSTEM.CPU.LOAD = ?
Error:agent dropped the connection
because of access permissions
IP:192.168.0.5 Server=127.0.0.1
I accept
connections only
from 127.0.0.1 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 12
AGENT LISTENER
Zabbix passive agent listens on TCP port 10050by default:
A different port can be specified using the "ListenPort" parameter
The agent listens on all available IP addresses by default:
It is possible to specify addresses that the agent should listen to
### Option: ListenPort
# Agent will listen on this port for connections from the server.
# Range: 1024-32767
ListenPort=10050
### Option: ListenIP
# List of comma delimited IP addresses that the agent should listen on.
#
# Mandatory: no
# Default:
ListenIP=0.0.0.0 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 13
MULTIPLE LISTENERS
For the C-based agent, multiple passive agent processes can be started at once:
Each process can respond only to a single request from a pollerat a time
More processes may be required if some of the checks are very slow
By default, 10 processes are started
Setting the "StartAgents" parameter to 0 disables the passive mode for the Zabbix agent
Agent 2 is already optimized for passive mode due to an improved architecture:
The built-in scheduler will execute the required number of tasks automatically
It is not possible to disable passive mode for Zabbix agent 2
### Option: StartAgents
# Number of pre-forked instances of zabbix_agentdthat process passive checks.
# If set to 0, disables passive checks and the agent will not listen on any TCP port.
## Range: 0-100
StartAgents=10 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 14
AGENT TIMEOUT
Agent timeout can be adjusted globally or per item using Zabbix frontend:
Unreasonable timeout increases may degrade monitoring performance
Agent pollerswill waste resources for unresponsive checks with large timeouts
5 seconds to
connect
Zabbix agentZabbix server
### Option: Timeout
Timeout=5
15 seconds to
collect data
Item
timeout
Zabbix server
configuration file [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 15
ADVANCED ZABBIX AGENT CONFIGURATIONS
Multiple hosts in the Zabbix instance can collect data from the same agent:
Sometimes it is useful to divide a physical server into multiple logical entities
Create as many hosts as needed and add Zabbix agent interface with the same address
The same agent
interface address
Zabbix server
with multiple
hosts
The same agent
answers all
requests [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 16
ADVANCED ZABBIX AGENT CONFIGURATIONS
Multiple Zabbix servers can collect data from the same agent:
Sometimes multiple Zabbix server instances are required (Prod, Test, etc.)
Agent can answer requests from multiple servers if they are specified in the configuration
zabbix-prod.example.com
zabbix-test.example.com
Server=zabbix-prod.example.com,zabbix-test.example.com
Agent configuration file [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 17
ZABBIX GET UTILITY
Command line utility "zabbix_get" may be used to connect to a passive agent:
A standalone utility that can be installed on any Linux or Windows workstation
Useful for troubleshooting agent availability or item keys
Can be integrated into custom scripts for data collection
The agent must accept connections from the machine executing "zabbix_get"
Additional parameters are available through the command: zabbix_get--help
# zabbix_get-s prod-server.example.com-k agent.version
7.0.0
agent.version= ?
7.0.0 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 18
1)Create a new Zabbix agent item on the Training-VM-XXhost:
▪key:system.cpu.util
▪tagcomponent : cpu
2)Test the item
3)Modify the Zabbix agent2 configuration file
▪Change Server address to: 127.0.0.1,student-XX.example.com
▪Test the agent2 configuration file.
▪Restart agent, then test item again
4)Create new Zabbix agent item to check available memory:
▪key:vm.memory.size[available]
▪tag:component : memory
5)Create new Zabbix agent item to monitor number of Zabbix processes:
▪key:proc.num[,zabbix]
▪tag:component : processes
6)Install zabbix-get utility and obtain metrics using zabbix_get
25 minutes 8
PRACTICAL TASK #8 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 19
ZABBIX AGENT ACTIVE MODE
15 mintes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 20
ZABBIX ACTIVE AGENT
In active mode, Zabbix agent initializes a connection to Zabbix server or proxy:
Active agent requests monitoring configuration by sending its Host name
Server responds with configuration (item keys and update intervals)
Agent collects metrics using received configuration and sends them back at regular
intervals
Hello, my Hostnameis "Web server", I need configuration
Hi "Web server", here is your list of monitored items
system.cpu.load= 0.75
net.if.in[eth0] = 143535
net.if.out[eth0] = 21414
OK, here are the metrics that I monitored
Zabbix agent Zabbix server [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 21
HOST CONFIGURATION
Settings for an active agent in Zabbix frontend:
Only the host name(not the visible name) is used to identify requests from active agents
Active agent does not require or use any interface
Host name
No interface [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 22
ITEM CONFIGURATION
To gather metrics using Zabbix agent active check:
Create an item with type "Zabbix agent (active)"
Specify item parameters (name, key, update interval. etc.)
The form is different and does not require any interface
Item
type [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 23
TRAPPER PROCESS
Data from the active agent is received by the Trapper process on Zabbix server:
This is a data collector that can catch data sent to Zabbix server
Trappers are very effective data collectors, one trapper can serve many active agents
Trappers by default listen on port 10051
### Option: StartTrappers
# Number of pre-forked instances of trappers.
# Trappers accept incoming connections from Zabbix sender, active agents and
# active proxies. At least one trapper process must be running to display
# server availability and view queue in the frontend.
# Range: 0-1000
# Default: 5
StartTrappers=10
### Option: ListenPort
# Listen port for trapper.
# Mandatory: no
# Range: 1024-32767
ListenPort=10051
Zabbix server configuration file
Zabbix server configuration file
/etc/zabbix/zabbix_server.conf [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 24
ACTIVE AGENT CONFIGURATION
There are two important parts in the active Zabbix agent configuration:
"ServerActive" must match the IP address or DNS name of Zabbix server or proxy
"Hostname" must match "Host name" in the Zabbix frontend
### Option: ServerActive
# Zabbix server/proxy address or cluster configuration to get active checks from.
# Server/proxy address is IP address or DNS name and optional port separated by colon.
# Multiple comma-delimited addresses can be provided to use several independent Zabbix servers
# in parallel. Spaces are allowed. If port is not specified, default port is used.
#
ServerActive=zabbix.example.com
### Option: Hostname
# List of comma delimited unique, case sensitive hostnames.
# Required for active checks and must match hostnames as configured on the server.
# Value is acquired from HostnameItemif undefined.
#
Hostname=Web server [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 25
SPECIFYING THE HOST NAME
There are three ways to specify a host name for an Active agent:
By using the "Hostname" parameter
By using the "HostnameItem" parameter to create the host name using an agent key
By commenting out both options and using system host name from the OS automatically
### Option: Hostname
# List of comma delimited unique, case sensitive hostnames.
# Required for active checks and must match hostnames as configured on the server.
# Value is acquired from HostnameItemif undefined.
Hostname=Web server
# Hostname=Web server
### Option: HostnameItem
# Item used for generating Hostname if it is undefined. Ignored if Hostname is defined.
# Does not support UserParametersor aliases.
HostnameItem=system.hostname[shorthost,lower]
# Hostname=Web server
# HostnameItem=system.hostname [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 26
ACTIVE AGENT CONNECTION
Zabbix active agent always initializes the connection:
Server is listening on port 10051 for incoming connections
Agent in active mode is not listening on any port
The data collection timeout is set by the monitoring configuration
Timeout in the agent configuration file is a communication timeout
Zabbix agent Zabbix server
StartTrappers=10
ListenPort=10051
ServerActive=zabbix.example.com
Hostname=Linux server
Timeout=5
Port
10051
5 seconds to connect
to Zabbix server
15 seconds
Item
timeout
Timeout from
configuration file [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 27
CONFIGURATION REFRESH
Agent retrieves a list of items from Zabbix server for independent processing:
On agent start, full configuration is always downloaded
When running, configuration is updated every 5 seconds, but only if changes were made
### Option: RefreshActiveChecks
# How often list of active checks is refreshed, in seconds.
#
# Mandatory: no
# Range: 1-86400
RefreshActiveChecks=5
Zabbix agent Zabbix server
Hello, my Hostnameis "Web server", I need configuration
Hello, my Hostnameis "Web server", are there new changes?
Hello, my Hostnameis "Web server", are there new changes? [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 28
SENDING COLLECTED DATA
Collected values are sent to Zabbix server or proxy in bulk:
Collected data are kept in the local buffer before sending (only for active mode)
Buffer content is sent every 5 seconds by default or when the buffer is full
Timestamps of data collection time using the host clock are preserved when sending data
Inaccurate clock on Zabbix agent may cause false alarms
Zabbix agent Zabbix server
timestamp = 1709553641, system.cpu.load= 0.75
timestamp = 1709553644, net.if.in[eth0] = 143535
timestamp = 1709553645, net.if.out[eth0] = 21414
Hello, my Hostnameis "Web server", here are the metrics
5 seconds of data [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 29
FORCE ACTIVE CHECKS ON START
Zabbix agent can be configured to send all item values after restart:
On a C-based agent, it is enabled by default and can not be disabled
Functionality on agent 2 is disabled by default and must be enabled manually
It may be useful because it is not possible to "Execute now" active agent items
Zabbix agent Zabbix server
I am sending all item values!
system.cpu.load= 0.75
net.if.in[eth0] = 143535
net.if.out[eth0] = 21414
.....
### Option: ForceActiveChecksOnStart
# Perform active checks immediately after restart for first received configuration.
# Also available as per plugin configuration
# Range: 0-1
# Default: 0
ForceActiveChecksOnStart=1 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 30
ACTIVE AGENT HEARTBEAT
Active agent is not using any interface but has its own availability status:
Availability is displayed using a virtual "Active checks" interface status
Status is calculated only using agent heartbeat messages (every 60 seconds by default)
Host must have at least one enabled active check to display the active check availability
Zabbix agent Zabbix server
Hello, I'm alive!
### Option: HeartbeatFrequency
# Frequency of heartbeat messages in seconds.
# Used for monitoring availability of active checks.
# 0 -heartbeat messages disabled.
# Range: 0-3600
HeartbeatFrequency=60 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 31
ACTIVE AGENT AVAILABILITY
It is possible to combine both active and passive agent items on the same host:
Both active and passive checks are executed simultaneously by the same agent
Agent will use different sections of the configuration file for communication
Availability icon will become a combination of both statuses in this case
Click on
the icon
for details
##### Passive checks related
Server=zabbix.example.com
##### Active checks related
ServerActive=zabbix.example.com
Hostname=Web server
Agent
configuration
example [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 32
MIXED CHECKS
On a mixed active / passive checks host, the availability color represents both:
Active agent checks are working, but the passive are failing
Active agent checks work, but passive agent checks are not defined
Used only by
simple checks
for example
Specific
scenario only
with agent [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 33
MULTIPLE HOSTNAMES
Agent in active mode may have multiple Hostnames simultaneously:
Zabbix agent in active mode may define multiple host names separated by commas
Agent will get configuration from both hosts and collect values for each of them
### Option: Hostname
# List of comma delimited unique, case sensitive hostnames.
# Required for active checks and must match hostnames as configured on the server.
# Value is acquired from HostnameItemif undefined.
# Mandatory: no
Hostname=Linux Server,Webserver
Zabbix agent Zabbix server
Metrics for the "Linux server" host
Metrics for the "Web server" host [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 34
MULTIPLE ZABBIX SERVERS
Agent in active mode may report to multiple Zabbix servers simultaneously:
Sometimes multiple Zabbix server instances are required (Prod, Test, etc.)
Zabbix agent in active mode may have multiple "ServerActive" defined
Agent will download separate monitoring configuration from each Zabbix server
### Option: ServerActive
# Zabbix server/proxy address or cluster configuration to get active checks from.
# Server/proxy address is IP address or DNS name and optional port separated by colon.
ServerActive=zabbix-prod.example.com,zabbix-test.example.com
Zabbix agent zabbix-test.example.com zabbix-prod.example.com [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 35
CONFIGURATION MISTAKES
Active agent misconfiguration:
Default host name "Zabbix server" used on multiple Zabbix active agents
Host name defined in agent configuration is not defined in Zabbix at all
The host is monitored by proxy, but Zabbix server address is used in "ServerActive"
The same Zabbix server is specified multiple times in "ServerActive"
### Option: ServerActive
# Zabbix server/proxy address or cluster configuration to get active checks from.
# Server/proxy address is IP address or DNS name and optional port separated by colon.
# Multiple comma-delimited addresses can be provided to use several independent Zabbix servers
# in parallel. Spaces are allowed. If port is not specified, default port is used.
ServerActive=127.0.0.1,zabbix.example.com
### Option: Hostname
# List of comma delimited unique, case sensitive hostnames.
# Required for active checks and must match hostnames as configured on the server.
# Value is acquired from HostnameItemif undefined.
Hostname=Zabbix server [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 36
1)On the host Training-VM-XX
▪Createa new Zabbix agent (active) item to check the Zabbix log directory size
▪key:vfs.dir.size[/var/log/zabbix/]
▪tag:component : disk
2)Check ''Latest data" for the Training-VM-XXhost
3)Configure Zabbix agent in the active mode
▪Change 'ServerActive' to student-XX.example.com
▪Change host name to 'Training-VM-XX'
▪Force active check refresh on restart
4)Create a new host Linux server
▪Link template "Linux by Zabbix agent active"
▪Host group: "Linux servers"
5)Check Linux server availability and latest values
6)Add host name"Linux server" to hostnames in agent configuration
7)Check Linux server availability and latest values
15 minutes 9
PRACTICAL TASK #9 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 37
USER PARAMETERS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 38
USER PARAMETERS
A "UserParameter" allows to perform custom checks in Zabbix:
Shell commands
Custom scripts
All commands are executed from the OS user which is used to run agent:
The user must have enough permissions to execute the command or script
The return value of the command is the standard output together with the standard error
User parameters are affected by the Zabbix agent timeout settings:
Long running scripts may negatively affect agent performance
C-based Zabbix agent in active mode has only a single data collector [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 39
USER PARAMETER CONFIGURATION
UserParameteris defined as an agent key, followed by the executed command
UserParameterrequires configuration on each Zabbix agent where it's utilized:
Directly in the zabbix_agentd.conffile
In a separate *.conf fileincluded in the zabbix_agentd.d/ zabbix_agent2.d directory
### Option: Include
# You may include individual files or
# all files in a directory
Include=/etc/zabbix/zabbix_agentd.d/*.conf
### Option: UserParameter
# User-defined parameter to monitor. There can be several user -defined parameters.
#
UserParameter=mykey,echo1
UserParameter=key,command
### Option: Include
# You may include individual files or
# all files in a directory
Include=/etc/zabbix/zabbix_agent2.d/*.conf [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 40
MULTIPLE USER PARAMETERS
More than one "UserParameter" can be defined per agent:
Multiple include files can be specified with different sets of parameters
All keys per agent must be unique or Zabbix agent will exit with the error message
Working directory for commands can be specified using a UserParameterDir:
"UserParameter" commands can be specified using the relative ./ prefix
Example: a script is located at /home/zabbix/workingdir/myscript.sh
ERROR: cannot add user parameter "mysql.qps,mysqladminstatus : key "mysql.qps" already exists
### Option: UserParameterDir
# When executing UserParametercommands the agent will change the working directory to the one
# specified in the UserParameterDiroption.
UserParameterDir=/home/zabbix/workingdir
UserParameter=mykey,./myscript.sh [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 41
RELOAD USER PARAMETERS
Zabbix agent needs the new item key loaded into the configuration to use it
To reload the list of user parameters, two methods are available:
Restart Zabbix agent to re-read the entire configuration file:
Use Zabbix agent runtime command "userparameter_reload":
▪Works for both Agent and Agent 2
▪Only user parameters are affected, other configuration changes are ignored
▪Not supported for zabbix_agentdon OpenBSD, NetBSD, or Windows
# systemctlrestart zabbix-agent
# zabbix_agent2 -R userparameter_reload
2024/06/26 09:30:37 User parameters reloaded
# systemctlrestart zabbix-agent2
# zabbix_agentd-R userparameter_reload
zabbix_agentd[52557]: command sent successfully [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 42
SIMPLE AND FLEXIBLE USER PARAMETERS
"UserParameter" can be simpleor flexible:
Simple user parameters do not have any arguments
Flexible user parameters accept one or multiple arguments(specified by *in the item key)
To use positional references unaltered, specify a double dollar sign.
In example $$1 will turn into $1 when executing the command.
UserParameter=mysql.qps,mysqladminstatus | cut -f9 -d":"
UserParameter=mysql.status[*],mysqladminstatus --user=$1--password=$2
UserParameter
has arguments [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 43
UNSAFE USER PARAMETERS
Certain symbols cannot be passed as arguments by default:
\' " ` * ? [ ] { } ~ $ ! & ; ( ) < > | # @
Additionally, newline characters are not allowed
### Option: UnsafeUserParameters
# Allow all characters to be passed in arguments to user -defined parameters.
# The following characters and newline characters are not allowed:
# \' " ` * ? [ ] { } ~ $ ! & ; ( ) < > | # @
# Range: 0-1
UnsafeUserParameters=0
0 = Deny
1 = Allow [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 44
1)Add a simple user parameter and restart Zabbix agent:
▪Key: mysql.uptime.s
▪Command line:
mysqladmin-uzabbix-pBlueSky67Fox!status 2>/dev/null | awk '{print $2}'
2)Add a new item to the Training-VM-XXhost to monitor this user parameter:
▪Name: MySQL Uptime (simple)
▪Tags: Name:application Value:mysql
3)Add a flexible user parameter to Zabbix agent without restarting it:
▪Key: mysql.uptime.f[*]
▪Command line: mysqladmin-u$1-p$2status 2>/dev/null | awk '{print $$2}'
4)Add a new item to the Training-VM-XXhost to monitor this user parameter:
▪Name: MySQL Uptime (flexible)
▪Tags: Name:application Value:mysql
▪Use macro to specify the username and secret macro to specify the password
15 minutes 10
PRACTICAL TASK #10 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 45
HUMAN-READABLE DATA
15 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 46
HUMAN-READABLE DATA
There are multiple ways to make collected values human-readable:
Add a unit of measurement with Item units
Transform raw values into more meaningful representations using Value maps
Visualization doesn't affect data processing or storage in the Zabbix database
1327506
15d 8h 58m 26s
1327506
4
in fault condition (4)
4
Item units Value maps [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 47
UNIT SYMBOLS
Unit symbols are used for a human-readable representation of data:
Can only be used with numerical data (unsigned/float)
If units are defined, K/M/G/T/P/E/Z/Y prefix fill be used with a multiplier of 1000
Try to store base units (bytes, seconds, etc.) to avoid strange results in the frontend
Stored in database Units Displayed in frontend
5000 Hz 5 KHz
5341623 bits 5.34 Mbits
3765986812 W 3.76 GW
1517888981633280 g 1.52 Pg
Stored in database Units Displayed in frontend
3200 MB 3.2 KMB
3435972078 B 3.2 GB [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 48
SPECIAL UNIT TYPES
Zabbix has five special hardcoded unit types:
B displayed with a multiplier of 1024
Bps displayed with a multiplier of 1024
unixtime displayed as a date
uptime displayed as a clock value
s displayed in textual time format
Stored in database Units Displayed in frontend
1024 B 1 KB
4096 Bps 4 KBps
1327506 uptime 15d 08:58:26
1327506 s 15d 8h 58m 26s
1706621596 unixtime 2024.01.30 13:33:16 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 49
THE ! PREFIX
To prevent any unit from being converted, you can use a ! prefix:
The value will be displayed exactly as it is, together with the unit symbol
Stored in
database
Units Displayed in frontend Units Displayed in frontend
5000 Hz 5 KHz !Hz 5000 Hz
614 s 10m 14s !s 614 s
1500 ms 1.5 Kms !ms 1500 ms
3435972078 B 3.2 GB !B 3435972078 B
3200 MB 3.2 KMB !MB 3200 MB [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 50
VALUE MAPS
Value maps contain the mapping between raw values and string representations:
Value maps are defined on the hostor templatelevel
Available value maps can be specified in the item configuration form
Can be used with items of the information type:
▪Numeric (unsigned)
▪Numeric (float)
▪Character
Problem started at 17:36:05 on 2024.07.13
Problem name: Zabbix agent is not available (for 3m)
Host: Linux server
Severity: Average
Operational data: not available (0) [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 51
MAPPING TYPES
Supported mapping types:
equals equal values
is greater than or equals equal or greater values
is less than or equals equal or smaller values
in range multiple ranges are supported (e.g., 1–10, 20–25)
regexp values corresponding to the PCRE regular expression
default all outstanding values [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 52
MULTIPLE MATCHED MAPPINGS
Usually, multiple mappings are defined per value map:
The mapping is applied according to the order of mapping rules
If multiple mappings overlap, the first match will be applied
It is possible to reorder mappings by dragging
"230" will be mapped as "Normal""230" will be mapped as "Perfect"
Value is
ignored [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 53
VALUE MAPS ON HOST OR TEMPLATE
Value maps can be defined on both the templateor hostlevel:
Items created on a host have access only to value maps defined on the host
A templated item has access to the value maps from the template
Hosts do not inherit value maps from linked templates
HOST
ITEM
ITEM
HOST VALUE
MAP
Template
TEMPLATE
VALUE MAP
ITEM
ITEM
ITEM
ITEM [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 54
On host Training-VM-XX
1)Add units '%' to the CPU utilizationitem
2)Add unit 'B' to Memory availableand Zabbix log directory sizeitems
3)Add unit 'uptime' to Mysqluptime flexibleitem
4)Add unit 's' to Mysqluptime simpleitem
5)Add units '!processes' to Number of zabbixprocessesitem
6)Create value map for SSHservice availability item (Up / Down)
7)Create value map for CPU Utilization item (Idle / Low / Medium / High / Overloaded)
15 minutes 11
PRACTICAL TASK #11 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 55
UPDATE INTERVALS
15 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 56
UPDATE INTERVAL
Update interval defines how often to retrieve a new value for
this item:
Minimum update interval is 1 second
Maximum allowed update interval is 1 day
Time suffixes are supported, e.g., 30s, 1m, 2h, 1d
Defaults to seconds if a suffix is not used (600 = 10m)
A user macro can be used in this field
Check CPU
utilization
every 10
seconds [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 57
UPDATE INTERVAL AND ITEM TYPES
Update interval can be set for most item types:
All item types where data collection is initialized by Zabbix server or proxy (passive items)
All Zabbix agent checks (both active and passive)
Update interval cannot be set for thefollowing item types:
Zabbix trappers pushed to Zabbix by 3rd party software
SNMP trappers pushed to Zabbix by SNMP device
Dependent items Is the same as for the master item
The "Update interval" field will be missing from the form if it cannot be set for
an item type [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 58
UPDATE INTERVAL
Update interval specifies the time betweenitem checks:
All checks are distributed equally over time
This design is implemented to prevent data collection spikes
Two items have the same update interval of 10 seconds:
Incoming traffic is monitored every 3rd, 13th, 23rd, 33rd, etc. second
Outgoing traffic is monitored every 6th, 16th, 26th, 36th, etc. second
The next created item will have different data collection times
02:31:03
time
02:30:5302:30:4302:30:33
02:30:36 02:30:46 02:30:56 02:31:06
10 seconds 10 seconds
Bits received
Bits sent [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 59
CUSTOM INTERVALS
Zabbix allows to customize item update interval using "Custom intervals":
Flexible intervals can redefine the update interval for specific time periods
Scheduling creates a custom polling schedule
Update interval, flexible intervals, and scheduled checks can be combined:
Update interval 0 is supported only in combination with custom intervals
Scheduled checks will be executed in addition to other intervals [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 60
FLEXIBLE INTERVALS
Flexible intervals let you redefine the default update interval for specific periods:
Interval the new update interval for the specified time period
Period the time period when the flexible interval is active
A single or multiple flexible intervals can be defined:
The default update interval is used outside the flexible intervals
In case of multiple overlapping intervals, the smallest interval value is used [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 61
!A massive use of scheduled items can cause big spikes on the monitored environment!
SCHEDULING INTERVALS
Scheduling intervals are used to check items precisely at specified times:
An additional independent checking schedule executed alongside "Update interval" checks
If the update interval is set to 0, only scheduled checks will be executed
every Monday till Friday at 9:00,10:00,...,18:00
11:00:00
time
10:00:0009:00:00 13:00:0012:00:00 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 62
SCHEDULING INTERVAL EXAMPLES
A scheduling interval is defined as:
md<filter>wd<filter>h<filter>m<filter>s<filter>
▪md month days 1-31
▪wd weekdays 1-7
▪h hours 0-23
▪m minutes 0-59
▪s seconds 0-59
<filter> is defined as: [<from>[-<to>]][/<step>]
Examples:
wd1-5h9 every Monday till Friday at 9:00
h9m/30;h10 execute at 9:00, 9:30, 10:00
h9-10m10-40/10 execute at 9:10, 9:20, 9:30, 9:40, 10:10, 10:20, 10:30, 10:40
md1wd1h9m30 every 1st day of each month at 9:30 if it is Monday [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 63
CUSTOM UPDATE INTERVAL TIME ZONE
Custom update intervals are supported:
For all item types where data collection is initialized by Zabbix server or proxy
As active or passive checks for both Zabbix agent and Zabbix agent 2
Zabbix server time zone is used to define custom interval periods:
Server time zone may be different from the time zone in the user profile
The "system.localtime[local]" item key may be used to check Zabbix server local time
Zabbix server
UTC (GMT+0)
John Doe
GMT-4
Zabbix server time zone is displayed
Why is data
collected
between
05:00 -14:00? [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 64
EXECUTE NOW
Pressing initiates an immediate item check upon request:
The value is collected and processed as usual
It can be executed for multiple items simultaneously
Executing a dependent item collects data from the master item instead
This functionality works both locally and through all types of Zabbix proxies
You can initiate this check from both the configuration and latest data views
Execute now
06:50:00
time
06:40:0006:30:0006:20:00
06:45:03
07:00:00
Execute now [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 65
!A green status message does not guarantee successful data collection
TASK EXECUTION
Pressing the button creates a data collection task:
The actual data collection may be delayed for a few seconds after pressing the button
The frontend reports the status of the task creation, not the result of data collection
The "Execute now" functionality is not available for:
Trapping items:
▪Zabbix agent (active)
▪Zabbix trapper
▪SNMP trapper
Disabled hosts and items
Zabbix agent
(active) [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 66
1)Add a flexible 5-second interval to the CPU utilization item
▪From Monday to Friday from 12:00 to 18:00
2)Change the interval for the Zabbix log directory size item
▪Collect item value at the beginning of every hour
▪Only on working days, from 9:00 to 18:00
5 minutes 12
PRACTICAL TASK #12 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 67
PREPROCESSING
5 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 68
PREPROCESSING
Preprocessingallows to define transformation rules for the received item values:
One or several transformations are possible
Transformations are executed in the order in which they are defined
The result of preprocessing is stored into the Zabbix database
Database Transformed dataCollected data Preprocessing [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 69
PREPROCESSING QUEUE
Only values with preprocessing steps goes through the preprocessing queue:
Collected data is placed into the waiting queue
The preprocessing manager assigns tasks from the waiting queue to workers
Preprocessing workers process all required preprocessing steps
Processed items are put into the processed queue and then transferred to the history cache
Preprocessing queue
Processed queue [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 70
PREPROCESSING WORKERS
Preprocessing can be performed by both Zabbix server and Zabbix proxies:
If a host is monitored by a proxy, preprocessing will be carried out by that proxy
Data already preprocessed by the proxy will bypass preprocessing on the server
Data without preprocessing steps will bypass preprocessing on the server and proxies
Preprocessing workers process items in parallel:
Some workers may become busy due to large data or complex preprocessing steps
Start additional preprocessors on Zabbix server or proxies if needed
### Option: StartPreprocessors
# Number of pre-started instances of preprocessing worker threads should be
# set to no less than the available CPU core count.
# More should be set if preprocessing is not CPU -bound and has lots of network requests.
# Range: 1-1000
# Default: 16
StartPreprocessors=32 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 71
COMMON PREPROCESSING STEPS
15 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 72
PREPROCESSING STEPS
Preprocessing steps are defined in a separate tab of the item configuration form:
The number of steps is displayed in the tab
The order of execution can be changed by dragging and dropping
Additionally, the type of information for the item is displayed:
It is possible to change the type of information without leaving the "Preprocessing" tab [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 73
CUSTOM ON FAIL
If a preprocessing step fails, multiple scenarios are possible:
Error handling can be introduced using "custom on fail" scenarios
Otherwise, the item will become unsupported, and no more steps will be processed
Custom on fail offers three options:
Discard value The value is discarded, and no more steps are processed
Set value to The value will be changed to the predefined value
Set error to The item will become not supported with a custom error [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 74
CUSTOM MULTIPLIER
Multiply or divide the value by the specified integer or floating-point value:
User macro can be used to specify the multiplier
Scientific notation is supported (e.g. 1e+70)
Division is possible if a multiplier < 1 is used
Notes for the Numeric (unsigned) item type:
Incoming values with a fractional part will be trimmed before multiplying
The result will also be trimmed before saving
256 * 0.125= 32128 * 8= 1024
numeric (unsigned) 2.5* 2.9= 2 * 2.9 = 5.8= 5
numeric (float) 2.5* 2.9= 7.25 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 75
ITEM VALUE CHANGE
Simple change computes the difference between the current and previous value
Change per second calculates the result based on the two latest values and time
A few important notes:
These steps can only be used for a constantly growing value
Zabbix does not store anything if the current value is smaller than the previous value
Only one change operation per item is allowed
Formula: value-previous value 135-80= 55
Formula:
value−previousvalue
time−previoustime
135−80
1600329600−1600329590
=
55
10
=5.5 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 76
USING COUNTERS
The following Zabbix agent keys report back metrics as counters:
net.if.in, net.if.out, net.if.total
system.cpu.intr, system.cpu.switches
system.swap.in, system.swap.out
Many other data collectors (e.g. SNMP) can also report data as counters
Without "change per second" With "change per second" [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 77
REGULAR EXPRESSIONS
Regular expression captures the matched text into a numbered group:
Zabbix supports the PCRE (Perl Compatible Regular Expressions) format
Both PCRE and PCRE2 libraries are supported
Regular expression supports extraction of a maximum of 10 captured groups:
An \N (where N=1…9) escape sequence is replaced with the Nth matched group
\0 escape sequence is replaced with the matched text
total used free
Mem: 1827840 75 Mem:\s+(\d+)\s+(\d+)\s+(\d+)
\0 = Mem: 1827 840 75 \1 = 1827 \2 = 840 \3 = 75
Source data Regular expression
Capturing groups [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 78
REGULAR EXPRESSION CONFIGURATION
In Zabbix frontend, two parameter fields must be specified:
Pattern -regular expression
Output -capturing group Regular expression Capturing group
Result can be
tested from the
frontend [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 79
DISCARD UNCHANGED VALUES
It is possible to discard unchanged values through preprocessing in Zabbix:
Zabbix will store and analyze data points only if the value has changed since the last check
Optionally, the heartbeat generates regular datapoints even without any data change
If preprocessing discards a value, Zabbix behaves as if no value was collected:
Graphs will have missing datapoints
If the history cache lacks values for an hour, trends cannot be calculated
Certain trigger functions may not work as intended
Database Collected data Preprocessing Discard value [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 80
DISCARD UNCHANGED WITH A HEARTBEAT
Time Values Discard unchanged
Discard unchanged
with heartbeat 30s
Explanation
00:00 0 0 0
00:05 0 No value because same as previous
00:10 0
00:15 1 1 1 Received different value
00:20 1
00:25 1
00:30 1
00:35 1
00:40 0 0 0 Received different value
00:45 0
00:50 0
00:55 0
01:00 0
01:05 0
01:10 0 0 Value written because of heartbeat 30s
01:15 0
01:20 1 1 1 Received different value
01:25 1
01:30 0 0 0 Received different value
01:35 0
01:40 0
01:45 0
01:50 0
01:55 0
02:00 0 0 Value written because of heartbeat 30s
02:05 0
30s
30s [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 81
ZABBIX PREPROCESSING COURSES
Automate your monitoring
workflows and scale your
Zabbix instance with high
availability in mind.
3 days
Prerequisites:
Zabbix Certified Specialist
exam or attendance
certificate
Advanced
Zabbix Data
Pre-Processing
Learn how to extract and
transform information from
different sources using
Zabbix built-in functionality
and without using external
tools or scripts.
1day
Prerequisites:
None
More preprocessing steps
are coveredin other
Zabbix training courses:
Zabbix 7.0 Certified Professional course:
▪XML Xpath
▪JSONPath
▪Prometheus patterns
▪Conversion to JSON
A specialized one-day preprocessing
course:
▪How preprocessing works internally
▪All preprocessing steps in much more detail
Zabbix
Certified
Professional [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 82
UNSUPPORTED ITEMS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 83
UNSUPPORTED ITEMS
Items in Zabbix may have a specific status called "Not supported":
Such items are in an error state and are not collecting data
"Not supported" is a specific value returned on each item check
Click on the error icon in the "Info" column to see details
Zabbix server
Unknown metric....
registry.get[....]
Zabbix agent
on Linux
I have no
idea what is
registry... [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 84
CHECK FOR NOT SUPPORTED VALUE STEP
Data collection errors can be fixed using "Check for not supported value" steps:
These steps are always executed before any other preprocessing steps
The "Custom on fail" option for this step provides various error-handling alternatives
Database
Transformed
data
Collected
data
Check for not
supported value
Custom
multiplier 8 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 85
CHECK FOR NOT SUPPORTED VALUE OPTIONS
"Check for not supported value" step provides three options:
Match any error
Match only errors with a specific pattern
Match only errors without a specific pattern
Multiple unique "Check for not supported value" steps can be added
Various error scenarios with a file monitoring item are checked [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 86
NOT SUPPORTED SCENARIOS
Items may become Not supported under multiple scenarios:
During data collection:
▪Wrong item key or parameters
▪Wrong credentials or permission problems
▪Data collection errors can be corrected by "Check for not supported value" preprocessing step
In preprocessing steps:
▪Failed regular expression, XML Xpathor JSONPath, incorrect Prometheus pattern
▪Arithmetical operations with character data
▪If a step fails, no more steps are processed
▪Use "custom on fail" options to override errors
When writing into database:
▪Wrong value type (writing text into numerical field, for example) [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 87
NOT SUPPORTED SCENARIOS
Unsupported item key
Non existing file
Wrong password
Wrong permissions
Preprocessing step failed Cannot write char to integer
"Check for not supported
value"
preprocessing step
"Custom on fail" option
Error cannot be
processed
Data collection Preprocessing Writing into DB
Fixable Fixable Non fixable [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 88
NOT SUPPORTED VS NOT AVAILABLE
Items will not be marked as "Not supported" if there is a communication error:
"Not supported" is an error returned due to a failed data collection/preprocessing
Communication errors will usually result in an unavailable host interface
agent.verison= ?
unknown item key
agent.version= ?
no response [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 89
1)On "Training-VM-XX", create a new item to monitor incoming traffic:
▪Update interval 10 seconds
▪Key: net.if.in[eth0]
▪Preprocessing: custom multiplier8
2)Check results
3)Add a preprocessing step to the incoming traffic item :
▪Preprocessing: change per second
4)Clear history for the incoming traffic item and check the result
5)Clone the incoming traffic item to monitor outgoing traffic
6)Add a preprocessing step to the SSH item Memory information:
▪Preprocessing: Check for not supported valueerror matchespassword
Custom on fail:set error toInvalid username or password!
20 minutes
PRACTICAL TASK #13
13 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 90
TRIGGERS
20 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 91
Triggers are logical expressions that "evaluate" data gathered by items:
Usually trigger expressions utilize a function with parameters and a threshold
A trigger may have one of the three statuses:
Normally the trigger is in the OKstatus
If data is out of the acceptable range, a trigger status changes to PROBLEM
If the trigger cannot be calculated, its status changes to UNKNOWN
TRIGGERS
avg (/production server/proc.num,10m) > 1000
Function Function parameters Threshold [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 92
CREATING A NEW TRIGGER
Triggers are created based on existing items:
Create a new trigger on a host or
template and set parameters:
▪Name
▪Event name
▪Operational data
▪Severity
▪Expression
▪OK event generation
▪Problem event generation mode
▪OK event closes
▪Allow manual close
▪Menu entry name
▪Menu entry URL
▪Description
▪Enabled [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 93
TRIGGER EXPRESSION SYNTAX
Trigger expressions use a unified expression syntax:
Expression uses a function that is applied to the item with certain parameters
The referenced item key must exist on the specified hostor template
The function result is compared to the threshold using an operator and a constant
function(/host or template/key,<additional parameters>)<operator><constant>
function( /host or template /key ,parameters )operator constant
last(/Zabbix server /system.uptime ) < 10m
min (/Linux by Zabbix agent/system.cpu.load[all], 5m ) >= {$CPU.LOAD}
avg(/Production server /vm.memory.utilization,{$PERIOD} ) > 1G
count(/MySQL database /log[/db/queries.log],1m, "like","error") > 50 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 94
TRIGGER CONDITION BUILDER
Trigger expressions can be built:
Manually, by entering the expression in the "Expression" field
Automatically, by using the trigger condition builder form
Condition
builder [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 95
OPERATORS
The following operatorsare supported for triggers:
Compare operations: <, <=, >, >=, =, <>
Change the sign with the unary minus:-
Mathematical operations: +, -, *, /
Lowercase logical operators : and, or, not
Notes:
Most operators expect numerical variables
Only the operators =or <>can be used to compare strings
Mathematical operations cannot be included within function arguments
min(/​host/​key,#5*10)min(/​host/​key,#5)*10
IncorrectCorrect [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 96
COMPARE ITEM VALUES
The compare <,<=,>,>=,=,<> operators can be used to compare item values
last(/Linux server/vfs.file.cksum[/etc/passwd],#1)<>last(/Linux server/vfs.file.cksum[/etc/passwd],#2)
Password has been changed
last(/Linux server/agent.version) <> '7.0.0'
Old Zabbix agent version
min(/Linux server/system.cpu.load,5m) > {$CPU.LOAD}
CPU load compared against User macro
last(/HA node1/hw.macaddr) = last(/HA node2/hw.macaddr)
Identical MAC addresses on two hosts [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 97
FUNCTION COMPARE
Triggers may be compared against the result of calculation (+,-, *, /)
CPU Load on Node 1 and Node 2 is unbalanced
High incoming network traffic on two nodes
avg(/HA Node 1/system.cpu.load[all,avg15],5m) < avg(/HA Node 2/system.cpu.load[all,avg15],5m) * 2
(avg(/HA Node 1/net.if.in[eth0],5m) +avg(/HA Node 2/net.if.in[eth0],5m)) >10G
Bytes are converted to bits before evaluation
avg(/router/net.if.in[eth0,bytes],​10m) * 8> 10M
Low available memory on database server
last(/DB Server/vm.memory.size[available]) /last(/DBServer/vm.memory.size[total]) < 0.1 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 98
COMBINE MULTIPLE ITEMS
Triggers may combine multiple items from the same or different hosts:
Logical operators and, or, notcan be used to join multiple conditions
Operators are case-sensitive and must be lowercase
last(/Linux server/system.cpu.load[all,avg1])>5 or min(/Linux server/system.cpu.load[all,avg1],10m)>2
min(/FRONTEND/system.cpu.load[all,avg1],5m)>2 and min(/MSSQLDB/mssql.lock_waits_sec.rate,5m)>0
and not (dayofweek()=7 and time()>230000)
and not (dayofweek()=1 and time()<010000)
Multiple CPU load conditions on the same host
Exclude Sunday and Monday
Conditions from different hosts
min(/WEB node 1/system.cpu.load[all,avg1],30m)>{$CPU.LOAD.MAX} and
min(/WEB node 2/vm.memory.size[available],30m)<{$MEMORY.AVAILABLE.MIN} [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 99
RESOLVING TRIGGER EVENTS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 100
RESOLVING PROBLEMS
Trigger may be resolved to "OK" state using different scenarios:
By using the trigger expression only, the trigger expression must become FALSE
By specifying an additional recovery expression
By manually closing the problem
Problem expression only
FALSE
Problem expression with recovery expression
FALSE TRUEAND [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 101
RECOVERY EXPRESSION
Recovery expression is calculated additionallyto a trigger expression:
The problem expression must become FALSEand the recovery expressionTRUE
If the problem expression is TRUErecovery expression is ignored
It is possible to create unwanted configuration where problem will never resolve
Correct Incorrect [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 102
RECOVERY EXPRESSION BENEFITS
A recovery expression may reduce trigger flapping:
Once a problem is detected, a different expression is used for recovery
Both Trigger and Recovery expressions are used for the OKevent calculation
0
0.5
1
1.5
2
2.5
3
3.5
9:00:009:00:109:00:209:00:309:00:409:00:509:01:009:01:109:01:209:01:309:01:409:01:509:02:00
CPU Load last(/host/system.cpu.load)>2 last(/host/system.cpu.load)<=1
Trigger
expression
Recovery
expression
Trigger expression
becomes TRUE
Trigger expression
becomes FALSE
Recovery expression
becomes TRUE [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 103
TRIGGER EVENTS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 104
TRIGGER EVENT TYPES
Each time the trigger changes its state, a new trigger event is generated:
When a trigger detects the problem, it creates a new Problem event
When the trigger detects that the problem is gone, it creates a Recovery event
PROBLEM
OK
Problem
EVENT
Recovery
EVENT [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 105
EVENT DETAILS
The event includes several details regarding the trigger state change:
Event name, Operational data, Severity, Time, Acknowledged, Tags, Description, Rank
The recovery event shows how the problem was resolved, either by the trigger or manually
Recovery
event
Problem
event [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 106
!Use multiple event generation for only for log files, SNMP traps and in other specific use cases
MULTIPLE EVENT GENERATION
Zabbix supports two event generation modes:
Single (default)only one event is generated –when a trigger goes into the Problem state
Multiple a new event is generated upon every evaluation of the trigger [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 107
TRIGGER NAME
The trigger name is mandatory:
It serves to quickly explain the trigger in the configuration view
The combination of trigger name and trigger expression must be unique per host
Trigger naming guide:
Keep the trigger name short and easy to understand
While some built-in macros and user macros can be used in the trigger name, it's not
recommended
Avoid using the {HOST.NAME} macro to keep names shorter
Do not use {ITEM.LASTVALUE} in trigger name, use the "Operational data" field
Use the "Event name" field to include thresholds and other relevant information [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 108
EVENT NAME
Event name is used to define the problem name generated by a trigger:
Can be used to build detailed problem names containing aggregated data
Event name supports the following set of macros:
▪Host name {HOST.HOST}, {HOST.NAME}
▪Host address {HOST.DNS}, {HOST.IP}, {HOST.CONN}, {HOST.PORT}
▪Collected value {ITEM.VALUE}, {ITEM.LASTVALUE}, {ITEM.LOG*}
▪Current time {TIME}
▪User macros {$MACRO}
▪Expression macros {?EXPRESSION} [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 109
TRIGGER AND EVENT NAMES
Trigger name is displayed in the host configuration:
By default, the event name is the same as the trigger name
Event name defines names of the problem and recovery events
PROBLEM NAME
PROBLEM EVENT
NAME
RECOVERY EVENT
NAME
EVENT NAMETRIGGER NAME [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 110
EXPRESSION MACROS
AND MACRO FUNCTIONS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 111
EXPRESSION MACROS
Expression macros are useful for formula calculations:
They are calculated on demand by Zabbix server or frontend
Expression macros have the following syntax
The expressionsyntax is the same as in trigger expressions
{?expression}
{?avg (/Production server/proc.num,10m) }
Function Function parameters [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 112
EXPRESSION MACRO DETAILS
Expression macros can have an expression containing:
Any of the supported functions (last, min, max, avg, etc.)
Any item key which exists on any host or template by using the /host/item syntax
User macros are not supported inside expression macros
Expression macros can be used in:
Trigger event names
Trigger-based notifications and commands
{?avg(/Production server/system.cpu.load,1h)}
{?last(//system.cpu.load)}
{?sum(/{HOST.HOST}/{ITEM.KEY},1h)}
Current host
can be omitted
by using the // [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 113
DISPLAYING ITEM VALUE
Built-in macros can be used to display the item value:
{ITEM.VALUE} the at-the-time-of-eventvalue
{ITEM.LASTVALUE} the most recent value
0
100
200
300
400
500
600
700
800
900
1000
9:00:009:00:109:00:209:00:309:00:409:00:509:01:009:01:109:01:209:01:309:01:409:01:509:02:00
Interface eth0: Bits in last(/host/net.if.in[eth0])>500M
{ITEM.VALUE}
{ITEM.LASTVALUE} [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 114
INDEX IN MACRO NAMES
Indexcan be used to specify first, second, etc. itemin trigger configuration:
{ITEM.VALUE<1-9>} the at-the-time-of-event value of the Nth item in the trigger expression
{ITEM.LASTVALUE<1-9>} the most recent value of the Nth item in the trigger expression
0
100
200
300
400
500
600
700
800
900
1000
9:00:009:00:109:00:209:00:309:00:409:00:509:01:009:01:109:01:209:01:309:01:409:01:509:02:00
Interface eth0: Bits inInterface eth0: Bits outlast(/host/net.if.in[eth0])>500M or last(/host/net.if.out[eth0])>500M
{ITEM.VALUE1}
{ITEM.VALUE2}
{ITEM.LASTVALUE1}
{ITEM.LASTVALUE2} [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 115
!Multiple macro functions in chain are not supported.
MACRO FUNCTIONS
The output of a macrocan be modified by using one of the macro functions:
▪fmtnum, fmttime Number or Time formatting
▪htmldecode, htmlencode Decoding / Encoding macro value into HTML encoding
▪urldecode, urlencode Decoding / Encoding macro value into URL encoding
▪regsub, iregsub, regrepl Substring extraction by a regular expression match
▪uppercase, lowercase Transformation into upper or lower case
▪tr Transliteration of macro value characters.
Macro functions are supported for all macro types:
▪Built-in macros
▪User macros
▪Low-level discovery macros
▪Expression macros
{{MACRO}.function(parameters)} [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 116
https://www.zabbix.com/documentation/7.0/en/manual/config/macros/macro_functions#fmtnum
NUMBER FORMATTING
The fmtnum() function can be applied to reduce number of digits:
The number is rounded to the specified number of digits
No trailing zeros will be produced
Macro syntax Macro value Output
{{?avg(//vm.memory.size[free],1h)}.fmtnum(2)} 24.3483523 24.35
{{ITEM.LASTVALUE}.fmtnum(0)} 8.245678 8
{{MACRO}.fmtnum(digits)}
0-20 digits [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 117
https://www.zabbix.com/documentation/7.0/en/manual/config/macros/macro_functions#fmttime
DATE FORMATTING
The fmttime() function can be applied to format time:
Compatible with strftimefunction formatting
Can be used with macros that resolve to a value in one of the following time formats:
▪hh:mm:ss
▪yyyy-mm-ddThh:mm:ss[tz] (ISO8601 standard)
▪UNIX timestamp
Macro syntax Macro value Output
{TIME} 1729506885 10:34:45
{{TIME}.fmttime(%B)} 1729506885 October
{{TIME}.fmttime(%d %B)} 1729506885 21 October
{{MACRO}.fmttime(format)} [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 118
1)On the host "Training-VM-XX", create a new item to monitor, 'CPU load'
▪Key: system.cpu.load
▪Update interval: 10 seconds
2)Create a trigger to detect a high CPU load
▪Condition: CPU load > 2
▪Use a user macro to define the trigger threshold
3)Use the stress command to test CPU load for 3 minutes
▪stress --cpu4 --timeout 180
4)Locate the problem in Zabbix frontend
▪Create a named filter for the problem generated by "Training-VM-XX"
▪Look at the graph for the item 'CPU load'
▪Look at the problem and recovery events
5)Add a recovery expression to the trigger
▪Condition: CPU load < 0.5
▪Use a user macro to define the trigger threshold
6)Test the new trigger configuration
10 minutes 14
PRACTICAL TASK #14 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 119
TRIGGER FUNCTIONS
15 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 120
FUNCTIONS
Zabbix supports almost 100 different functions:
Aggregate functions avg, count, min, max, sum, kurtosis, etc.
Bitwise functions bitand, bitlshift, bitnot, bitor, bitrshift, bitxor
Date and time functions date, dayofmonth, dayofweek, now, time
History functions last, first, change, logseverity, monoinc, nodata, etc.
Trend-based functions trendavg, trendcount, trendmax, trendmin, trendsum, etc.
Mathematical functions abs, cos, sin, tan, ceil, floor, degrees, e, exp, log, rand, etc.
Operator functions in, between
Prediction functions forecast, timeleft
String functions ascii, bitlength, char, concat, find, left, length, trim, mid, etc.
Foreach functions* avg_foreach, last_foreach, sum_foreach, etc.
*can be used only in calculated items [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 121
FUNCTION PARAMETERS
Most of the functions require one or multiple parameters:
The /host/keyis a common mandatory first parameter for history functions
Some functions do not require additional parameters
Other parameters are placed after the /host/keyseparated by a comma:
If an evaluation period or range is required, it always goes as a second parameter
More than one parameter may be used for some functions
min(/prod/vm.memory.size[free],1h)
count(/prod/log[/var/log/myApp.log],10m,"like","error")
last(/prod/system.cpu.load) [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 122
TIME PERIODS
Most numeric functions accept timeor number of values as a parameter:
Seconds will be used if no time suffix is specified
Time suffixes may be used to specify time units (10s, 5m, 1h, 7d, etc.)
If preceded by a hashtag #, the parameter indicates the number of values (#5, #10, etc.)
Parameter syntax Description
sum(/host/key,10s) Sum of values in the last 10 seconds
sum(/host/key,10m) Sum of values in the last 10 minutes
sum(/host/key,1h) Sum of values in the last hour
sum(/host/key,#10) Sum of the last 10 values
sum(/host/key,10) Sum of values in the last 10 seconds
Syntax without
time units can be
confusing [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 123
FUNCTION PARAMETERS
Example:
Item update interval is 5 seconds
Item is collected every minute at 00, 05, 10, 15, etc.
time
35 40 45* 50 55 00 05 10 15 20 25 30 35* 40 45
max(/host/key,1m)
302520
09:05:00 09:05:45
min(/host/key,#10)
avg(/host/key,10)
*these values are not included in the calculation [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 124
VALUE AND TREND FUNCTION CACHES
Most trigger functions are evaluated based on historical data:
All data for the evaluation period is stored in the "Value cache" on Zabbix server
Some functions use trends for long-term analytics (trendavg(), trendcount(), etc.):
These functions use trend data from the "TrendFunctionCache" on Zabbix server
Recommended to use for long periods to not fill the Value cache with thousands of values
avg(/Linux server/vm.memory.size[free],3h) < 200M
15 30 45 00 15 30 45 00 15 30 45 00 15 30 45
06:05:45 09:05:45
all collected values for last 3 hours
Value
cache [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 125
VALUE AND TREND FUNCTION CACHE CONFIGURATION
Value cache size is defined in the Zabbix server configuration file:
Running out of value cache may seriously degrade Zabbix performance
Zabbix automatically will detect issues with value cache and create a problem
Increase the Value cache size and restart Zabbix server
Trend function cache size is defined in the Zabbix server configuration file
### Option: TrendFunctionCacheSize
# Size of trend function cache, in bytes.
# Shared memory size for caching calculated trend function data.
# Range: 128K-2G
TrendFunctionCacheSize=4M
### Option: ValueCacheSize
# Size of history value cache, in bytes.
# Shared memory size for caching item history data requests.
# Setting to 0 disables value cache.
# Range: 0,128K-64G
ValueCacheSize=16M [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 126
DATA REQUIREMENTS
Trigger is calculated if some data exists in the evaluation period:
The average from 10 values can be calculated if at least a single value is collected
avg(/Linux server/system.cpu.load,#10) > 2
15 30 45 00 15 30 45 00 15 30 45 00 15 30 45
06:05:45 09:05:45
Only 3
values are
enough
7 more values not yet collected
Item
created [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 127
UNKNOWN TRIGGERS
Triggers functions cannot be calculated in the following scenarios:
The referenced item is in a "not supported" status (except the nodata() function)
The function evaluation for a supported item results in an error
No data exists in the evaluation period [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 128
TIME-BASED FUNCTIONS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 129
DATE AND TIME FUNCTIONS
All date and time functions are time-based:
date current date in YYYYMMDD format
time current time in HHMMSS format
dayofweek current day of week 1-7 (Mon -1, Sun -7)
dayofmonth current day of the month 1-31
now seconds since the 00:00:00 UTC January 1, 1970
These functions can be used to specify time periods in trigger calculation:
Detect problems only on weekends
Ignore scheduled backups between 01:00:00 and 03:00:00
avg(/host/system.cpu.util[,iowait],5m) > 5 and (time() < 010000 or time() > 030000)
min(/host/system.cpu.load,30s) > 2 and dayofweek() > 5 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 130
TIME-BASED FUNCTIONS
All time-based functions are recalculated every 30 seconds:
Recalculation schedule is distributed evenly between all time-based functions
Using lots of time-based functions may negatively affect Zabbix performance
If both time-based and non-time-based functions are used in an expression:
It is recalculated when a new value is received
Additional calculation is done additionally every 30 seconds
min(/Linux server/system.cpu.load,1m) > 2 and dayofweek()> 5
Regular function Time-based function [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 131
TRIGGER EXAMPLE
Example trigger with both regular and time-based functions:
Recalculated every 10 seconds based on the item update interval
Additionally recalculated every 30 seconds because a time-based function is used
Time based function
Regular function
0
0.5
1
1.5
2
9:00:009:00:109:00:209:00:309:00:409:00:509:01:009:01:109:01:209:01:309:01:409:01:509:02:00
min(/host/system.cpu.load,1m) > 2 and dayofweek() > 5
30 seconds [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 132
NODATA() FUNCTION
Nodata() history function checks for the absence of data received:
The time period should not be less than 30 seconds (nodata(0) is not allowed)
if mode is set to "strict", this function will be insensitive to proxy availability
Nodatafunction returns:
1 -if no data is received during the defined period of time
0 -otherwise
nodata(/host/key,timeperiod,<mode>)
nodata(/Linux by Zabbix agent active/agent.ping,5m)=1
No agent.pingvalues
received in 5 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 133
NODATA() AND PROXY AVAILABILITY
The 'nodata' triggers monitored by proxy are sensitive to proxy availability:
They will not trigger if the data is expected from a proxy, which is currently offline
By setting the <mode> parameter to "strict" mode, proxy availability will be ignored
No problems are
detected using
nodata() triggers [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 134
NODATA EXAMPLE
The nodata() function can be used to detect:
Zabbix agent availability (agent.pingitem never returns 0)
Changes in the log files monitored by Zabbix
Data received (or not received) on the regular intervals
0
1
2
9:01:15 9:02:15 9:03:15 9:04:15 9:05:15 9:06:15 9:07:15
Zabbix agent ping nodata(/host/agent.ping,2m)=1
2 minutes of no data
received
The problem is
resolved
immediately when
the data arrives [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 135
!The nodata() function is evaluated even for "not supported" items
NOTES
TheZabbix server time zone is used to calculate time-based functions:
User time zone settings may differ from the Zabbix server time zone
Time-based functions in triggers with multiple event generation mode will
create a new problem every 30 seconds:
The trigger will be evaluated every 30 seconds even if any new data isn't received
This will generate a new problem whenever the expression result is true
The nodata() function may produce false positives if:
There are time differences between the Zabbix server, proxy, and agent
"Discard unchanged" preprocessing steps are applied in item configuration
History is not saved for the item [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 136
1)Change the update interval for the Memory available item:
▪Update interval: 10 seconds
2)Create a trigger to detect low available memory with average severity:
▪Condition: max(Available memory,1m) < 100 M
▪Use a user macro to define the trigger threshold
3)Test the trigger
▪stress -m 1 --vm-bytes 2G --timeout 180
4)Create a new item,Zabbix agent ping:
▪Key: agent.ping
▪Update interval: 10 seconds
5)Create a trigger to check the status ofZabbix agent ping with the severity 'Information'
▪Function last(agent.ping) = 0
6)Stop Zabbix agent 2 and:
▪Look for problems detected by the trigger
▪Change the trigger function to nodata(1m)
▪Look again for problems detected by the trigger
15 minutes 15
PRACTICAL TASK #15 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 137
PROBLEMS
15 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 138
PROBLEMS
Problems are generated based on events:
Problem event will createa new problem
Recovery event will resolvethe problem
Problem duration is the time between problem and recovery
events
0.00
1.00
2.00
3.00
4.00
5.00
6.00
9:00:00 AM9:00:10 AM9:00:20 AM9:00:30 AM9:00:40 AM9:00:50 AM9:01:00 AM
PROBLEM
EVENT
RECOVERY
EVENT
Problem duration = 00:00:50
Trigger
CPU load > 2 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 139
PROBLEM FILTER
Problems are displayed on the "Monitoring" > "Problems" page:
The top section of the page contains a huge set of different filters
Filters can be saved as additional tabs and reused later
The number of active problems can be displayed on the tab [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 140
PROBLEMS PAGE
The main part of the "Problems" page contains the list of the current problems:
The representation of problems depends on the global filter
Recent problems active problems and problems resolved in the last 5 minutes
Problems only active problems
History custom history period for problems can be specified [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 141
OPERATIONAL DATA
Operational data is used to display live values on the "Problems" page:
Macros in the trigger name will resolve to values at the time of problem creation
Macros in the operational data will display the very latest information dynamically
The same set of macros is supported as in the trigger name
If undefined, it will display {ITEM.LASTVALUE} from all items used in expressions
Event name Last value
Multiple values [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 142
PROBLEM UPDATE
Status of a problem can be changed by:
Adding a text message
Changing problem severity
Acknowledging
Manually closing (if allowed)
All problem updates are displayed in frontend:
Comments have been made
Problem acknowledged
Problem severity changed
Actions have been taken [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 143
PROBLEM DISPLAYING OPTIONS
Go to the "Administration" > "General" > "Trigger" displaying options:
Redefine event status colors
Change problem display options
Change trigger severity names and colors [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 144
SUPPRESS PROBLEM
A problem can be manually suppressed using problem updates:
Indefinitely, until closed, or until manually unsuppressed
Until a specified time (relative or absolute)
A problem may be unsuppressed through the same window
Suppressed problem functionality:
They can be filtered out on the "Problems" page
Action execution can be paused for the suppressed period
Suppress
problem
Problem is
suppressed [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 145
CLOSE PROBLEM
Problems can be manually closed:
Manual close must be allowed in trigger configuration
When the trigger expression is re-evaluated, it may result in a new
problem
0
0.5
1
1.5
2
2.5
3
3.5
4
4.5
5
5.5
6
9:00:009:00:109:00:209:00:309:00:409:00:509:01:009:01:109:01:209:01:309:01:40
CPU Load last(/host/system.cpu.load)>2
Manual
close [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 146
CAUSE AND SYMPTOM
PROBLEMS
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 147
CAUSE AND SYMPTOM PROBLEMS
Problems in Zabbix can be classified as Causeor Symptomproblems
Database
down
Web page
unavailable
Application
unavailable
Cause Symptoms [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 148
CAUSE AND SYMPTOM PROBLEMS DISPLAY
Symptom problems are displayed below the cause problem:
They are marked with theicon, smaller font, and a different background
In the collapsed view, only the cause problem and number of symptoms is displayed
Number of
symptoms [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 149
CAUSE AND SYMPTOM PROBLEM CLASSIFICATION
By default, all new problems are classified as cause problems:
Problems must be manually reclassified as symptom problems
Only cause problems are counted in problem totals in maps, dashboard widgets, etc.
A symptom problem can be linked to only one cause problem:
The cause-symptom hierarchy supports only two levels
A problem that is already a symptom cannot be linked to consequent symptoms [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 150
SYMPTOM AND CAUSE PROBLEM RESOLVING
Symptom problems are not automatically resolved, if the cause problem is
resolved or closed:
Each problem is evaluated separately
Symptoms will not become cause problems if their cause is resolved
Only cause is resolved [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 151
CLASSIFY AS A SYMPTOM
To classify a problem as a symptom problem, follow these simple steps:
First, select the symptom (or symptoms) in the list of problems
Next, find the cause problem
In the context menu of the cause problem, click on the 'Mark selected as symptoms' option
Select
symptoms
Click on the problem
name to open context
menu [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 152
REVERT BACK TO CAUSE
A symptom problem can be reverted back to a cause problem in two ways:
By clicking on the "Mark as cause" option in the context menu of the symptom problem
By marking the "Convert to cause" option in the problem update screen
Click on the problem
name to open context
menu
Click on
Update [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 153
TRIGGER DEPENDENCIES
10 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 154
TRIGGER DEPENDENCIES
A trigger may have one or more triggers it depends on:
Problems will be suppressed if the trigger they depend on is in the
PROBLEM state
Zabbix does not support dependencies between hosts directly
While the parent trigger is in the PROBLEM state, its dependent triggers
will not be re-evaluated
They will be re-evaluated only when the parent trigger:
Goes back from the PROBLEM to the OK or UNKNOWN state
Is closed manually
Is disabled (by disabling the item, trigger, or host) [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 155
TRIGGER DEPENDENCIES
Dependencies between triggers can be defined:
Between triggers on the same host
Between triggers on different hosts
Dependencies between triggers on different hosts Dependencies between
triggers on the same host
Router
Switch B
Server 4
Switch A
Server 3
Server 1
Low disk space
Very low disk space
Out of disk space
Server 2 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 156
TRIGGER DEPENDENCIES
Problems generated by the dependent triggers will be hidden:
They will be not displayed on the Problems page
Notifications of the dependents will be skipped
Problems will be displayed with dependent and parent triggers (if they exist) [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Theory 157
DEFINE A DEPENDENCY
To define a trigger dependency:
Open the "Dependencies" tab in the trigger configuration form
Click on Addin the "Dependencies" block
Select one or more triggers that the trigger will depend on
Click on
Add
Select new
dependency [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 Practical task No: 158
1)Create a new item to monitor the number of stressprocesses running
▪Item key proc.num[stress]
2)Create a new trigger for the running stresscommand:
▪function: last(proc.num[stress]) > 0
3)Use the stresscommand to test memory usage for 10 minutes
▪stress -m 1 --vm-bytes 2G --timeout 600
4)Wait for the problem to appear
▪Mark the CPU and memory problems as symptoms to the stress problem
▪Acknowledge the problem
▪Increase the severity of the problem
▪Close the problem
5)Create a new trigger for 'very high CPU load'
▪Condition: CPU load > 3
▪Use a user macro to define the trigger threshold
6)Create a dependency between high and very high CPU load triggers, and test it
20 minutes
PRACTICAL TASK #16
16 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2 159
Questions?
15 minutes [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

© 2025by Zabbix. All rights reserved7.0 Certified Specialist ■Day 2
Thank you!
End of Day 2 [email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
Powered by TCPDF (www.tcpdf.org)
Tags
Categories
Education
Download
Download Slideshow Get the original presentation file
Quick Actions
Statistics
  • Views 13
  • Slides 160
  • Age 95 days
Related Slideshows
TLE-9-Prepare-Salad-and-Dressing.pptxkkk 11
TLE-9-Prepare-Salad-and-Dressing.pptxkkk
MaAngelicaCanceran
61 views
LESSON 1 ABOUT MEDIA AND INFORMATION.pptx 12
LESSON 1 ABOUT MEDIA AND INFORMATION.pptx
JojitGueta
45 views
GRADE-8-AQUACULTURE-WEEKQ1.pdfdfawgwyrsewru 60
GRADE-8-AQUACULTURE-WEEKQ1.pdfdfawgwyrsewru
MaAngelicaCanceran
76 views
Feelings PP Game FOR CHILDREN IN ELEMENTARY SCHOOL.pptx 26
Feelings PP Game FOR CHILDREN IN ELEMENTARY SCHOOL.pptx
KaistaGlow
67 views
Jeopardy_Figures_of_Speech_Template.pptx [Autosaved].pptx 54
Jeopardy_Figures_of_Speech_Template.pptx [Autosaved].pptx
acecamero20
38 views
Jeopardy_Figures_of_Speech.pptxvdsvdsvsdvsd 7
Jeopardy_Figures_of_Speech.pptxvdsvdsvsdvsd
acecamero20
41 views
View More in This Category