Zabbix templates
This repository provides a set of templates which offers the alternative set of templates to supplied by Zabbix.
On master branch is last stable version of the templates. Please report eny found issues or bugs.
Development of the next version of the templates is done on devel branch.
If you have some changes for those templates please submit PR against devel.
Table of Contents
- Changelog
- List of templates
- Notes and Guidlines
-
Changelog:
1.0.4 (2018-06-11)
- The first version tagged in git repo to stamp state of templates and tools and to provide better tracking changes by using
git
command - The development of the next versions of the templates will continue on devel branch. When all changes are ready devel branch will be merged to master one. It will be way better for those who have interested enough tested template.
-
Recent changes
- All templates:
- change all graphs resolution to 1200x300
- ICMP
- Screens:
- new
NET::ICMP
- new
- Screens:
- MIB
- changed all description OID trees URLs to http://www.oidview.com/mibs/ based (http://support.ipmonitor.com seems no longer available)
- IF-MIB
- Applications:
- the new prototype for all
interfaces
LLD prototype itemsIF-MIB::interfaces::{#IFDESCR}
- the new prototype for all
- LLDs:
- new
interfaces
LLDdiscovery[{#IFDESCR},IF-MIB::ifDescr,{#IFOPERSTATUS},IF-MIB::ifOperStatus]
and added filter to remove from the list all interfaces with ifOperStatus=Down state. Switch from to as macro indexing all prototype items
- new
- Screens:
- new:
IF-MIB::ifHCOctets
IF-MIB::ifOctets
- new:
- Applications:
- SNMPv2-MIB
- Applications:
- rename mib-2.system to
SNMPv2-MIB::system
and mib-2.system.snmp to ‘‘‘SNMPv2-MIB::snmp’’’ to use matching MIB naming conventoion
- rename mib-2.system to
- Items:
- changed units in update interval from number of seconds to number of m/h/d
- Graphs:
- new normal graph
SNMPv2-MIB::snmpPkts
with SNMPv2-MIB::snmp{in,Out}Pkts OIDs presenting rate of SNMP requests/replies
- new normal graph
- Applications:
- OS Linux
- Items:
- added
MEM::
items descriptions - fixed
NET::segments retransmitted
item use new sed regexp in this items/\( *\)\(.*\) segments retransmitted*/\2/ p/
- added
- Triggers:
- fixed typo in name: s/SYS:uname changed/
SYS::uname changed
/ - rename “Lack of free memory” to
MEM::free {ITEM.LASTVALUE}
- use
diff()
=1 function (insteadchange()
andstr()
) in triggers:HW::devices list has been changed
HW::CPU info has changed
- fixed typo in name: s/SYS:uname changed/
- Items:
- OS Solaris
- Triggers:
- fixed typo in trigger name s/SYS:uname changed/
SYS::uname changed
/ - added
MEM::free {ITEM.LASTVALUE}
- fixed typo in trigger name s/SYS:uname changed/
- Triggers:
- OS Windows
- Triggers:
- rename trigger to the same name as it is in other OS templates s/Host information was changed/
SYS:uname changed
/ - rename “Lack of free memory” to
MEM::free {ITEM.LASTVALUE}
- rename trigger to the same name as it is in other OS templates s/Host information was changed/
- Triggers:
- Service MySQL
- Applications:
- new:
SVC::MySQL::cfg
for all read configuration parametersSVC::MySQL::Com
for all Com_* metricsSVC::MySQL::DB::{#DB}
prototype for all per database metricsSVC::MySQL::innodb
for all innodb storage engine metricsSVC::MySQL::threads
for all treads related metrics
- Graphs:
- new
SVC::MySQL::threads
withThreads_cached
,Threads_connected
andThreads_running
metrics
- new
- Items:
- new
max_allowed_packet
- the maximum size of one packet or any generated/intermediate string - new
show_compatibility_56
- show is MySQL engine running in MySQL 5.6 compatibility mode is ON/OFF - new
Threads_cached
- the number of threads in the thread cache - mew
Threads_running
- the number of threads that are not sleeping - rewrite most of the items SQL queries to use uppercase SQL keywords and lowercase for table names and row names (this will cause problems with imprt new template b ut I need to standarize thuis before first officially announced release of the templates)
- new
- Screens:
- new
SVC::MySQL::threads
which combinesSVC::MySQL::threads
graph andConnections
simple graph
- new
- Triggers:
- new
SVC::MySQL::version
has been changed (severity: Not classified) - new
SVC::MySQL::cfg::show_compatibility_56=ON
(severity: High, because this template requires show_compatibility_56=OFF)
- new
- Applications:
- Service Zabbix Proxy
- Applications:
- new
SVC::Zabbix Proxy::proc
- new
- Graphs:
- updated:
SVC::zabbix_proxy::process busy %
SVC::zabbix_proxy::data gathering process busy %
- updated:
- Items:
- new:
proc::busy::configuration syncer
proc::busy::data sender
proc::busy::heartbeat sender
proc::busy::ipmi manager
proc::busy::ipmi poller
proc::busy::java poller
proc::busy::snmp trapper
wcache::index::pfree
- delete items which have been by mistake copied from Service Zabbix Server template
wcache::text::free
wcache::text::total
wcache::text::used
- move
Processes::
items toSVC::Zabbix Proxy::proc
Application - rename all
Processes::$4::$2
toproc::$4::$2
and remove quotes on all those items second key parameter (to allow easy migration from standard “Template App Zabbix Proxy” template)
- new:
- Triggers:
- new:
SVC::zabbix_proxy::configuration syncer >=75% busy
SVC::zabbix_proxy::data sender >=75% busy
SVC::zabbix_proxy::heartbeat sender >=75% busy
SVC::zabbix_proxy::ipmi manager >=75% busy
SVC::zabbix_proxy::ipmi poller >=75% busy
SVC::zabbix_proxy::java poller >=75% busy
SVC::zabbix_proxy::snmp trapper >=75% busy
SVC::zabbix_proxy::vmware collector >=75% busy
- new:
- Applications:
- Service Zabbix Server
- Applications:
- new:
SVC::Zabbix Server::rcache::buffer
SVC::Zabbix Server::vcache::buffer
SVC::Zabbix Server::vcache::cache
SVC::Zabbix Server::wcache::history
SVC::Zabbix Server::wcache::trend
SVC::Zabbix Server::wcache::values
- rename
SVC::Zabbix Server::process::busy
toSVC::Zabbix Server::proc
- new:
- Graphs:
- updated
SVC::zabbix_server::process busy %
- new
SVC::zabbix_server::preprocessing queue
- updated
- Items:
- added all items descriptions
- new:
proc::busy::alert manager %
proc::busy::escalator %
proc::busy::ipmi manager %
proc::busy::ipmi poller %
proc::busy::java poller %
proc::busy::preprocessing manager %
proc::busy::preprocessing worker %
proc::busy::proxy poller %
proc::busy::snmp trapper poller %
proc::busy::task manager %
proc::busy::timer %
proc::busy::vmware collector %
triggers
queue::preprocessing
- remove items::queued (it duplicates information provided by queue::* items)
- removed quotes around processes names to make migration from standard zabbix template easier
- rename all process::* items to
proc::*
(keep it in sync with proxy template) - rename Uptime to
uptime
- Triggers:
- new:
SVC::zabbix_server::alert manager processes >=75% busy
SVC::zabbix_server::escalator processes >=75% busy
SVC::zabbix_server::ipmi manager processes >=75% busy
SVC::zabbix_server::ipmi poller processes >=75% busy
SVC::zabbix_server::java poller processes >=75% busy
SVC::zabbix_server::preprocessing manager processes >=75% busy
SVC::zabbix_server::preprocessing worker processes >=75% busy
SVC::zabbix_server::proxy poller processes >=75% busy
SVC::zabbix_server::snmp trapper processes >=75% busy
SVC::zabbix_server::task manager processes >=75% busy
SVC::zabbix_server::timer processes >=75% busy
SVC::zabbix_server::vmware collector processes >=75% busy
- new:
- Applications:
-
Service Nginx
- All templates:
- ICMP
- MIB
- OS Linux
- OS Solaris
- OS Windows
- SNMP Devices
- BIG-IP 5000
- DSL-3782
- Service Apache
- Service MySQL
- Service Nginx
- Service Zabbix Agent
- Service Zabbix Proxy
- Service Zabbix Server
Notes and Guidelines:
- Each template has own version tag which is the copy of the whole zabbix-templates package version tag in which last changes has released
- Each template in the description field has the last modification date and internal version
- If it is something which needs to be done to use those templates it is described in each template within description notes
-
Naming convention for the items names, applications and triggers must adhere naming convention using 2-4 letter abbreviations:
<CLASS>::<Name> <CLASS>::<SUBCLASS>::<Name>
Items Examples:
HW::CPU MEM::Total Memory NET::ICMP::Loss NTP::WTS::Clock Frequency Adjustment
Above provide a parseable name, allowing us to distinguish between and categorise those objects. Such convention allows to handle use the pattern in alarming layer allowing on define actions. For example, send all trigger with SYS:: in the beginning name of the template to exact team. Such pattern is possible to use as part of the general interface on communication with external services.
- Do not use macros in triggers. In web frontend from Monitoring -> Triggers table has “host” column with the host name of the the active trigger. Repeating second time this hos name in the trigger name it is waste of space on the web page.
- All zabbix agent items should be specified as
zabbix agent (active)
items. - All graphs resolution needs to be 1200x300.
- All SNMP items should be as SNMPv2 and
{$SNMP_COMMUNITY}
as SNMP read community name.
Reason of use in all templates the same graphs resolution, item types and SNMP protocol version and community name is to provide easy way to change those settings across all templates is someone may need this.