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.

Changelog
- 1.0.4
List of templates
Notes and Guidlines
Copyright

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
- 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 items IF-MIB::interfaces::{#IFDESCR}
    - LLDs:
      - new interfaces LLD discovery[{#IFDESCR},IF-MIB::ifDescr,{#IFOPERSTATUS},IF-MIB::ifOperStatus] and added filter to remove from the list all interfaces with ifOperStatus=Down state. Switch from {#SNMPVALUE} to {#IFDESCR} as macro indexing all prototype items
    - Screens:
      - new:
        
        IF-MIB::ifHCOctets
        
        IF-MIB::ifOctets
  - 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
    - 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
- OS Linux
  - Items:
    - added MEM:: items descriptions
    - fixed NET::segments retransmitted item use new sed regexp in this item s/$ *$$.*$ segments retransmitted*/\2/ p/
  - 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 (instead change() and str()) in triggers:
      - HW::devices list has been changed
      - HW::CPU info has changed
- OS Solaris
  - Triggers:
    - fixed typo in trigger name s/SYS:uname changed/SYS::uname changed/
    - added MEM::free {ITEM.LASTVALUE}
- 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}
- Service MySQL
  - Applications:
    - new:
    - SVC::MySQL::cfg for all read configuration parameters
    - SVC::MySQL::Com for all Com_* metrics
    - SVC::MySQL::DB::{#DB} prototype for all per database metrics
    - SVC::MySQL::innodb for all innodb storage engine metrics
    - SVC::MySQL::threads for all treads related metrics
  - Graphs:
    - new SVC::MySQL::threads with Threads_cached, Threads_connected and Threads_running metrics
  - 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)
  - Screens:
    - new SVC::MySQL::threads which combines SVC::MySQL::threads graph and Connections simple graph
  - 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)
- Service Zabbix Proxy
  - Applications:
    - new SVC::Zabbix Proxy::proc
  - Graphs:
    - updated:
      - SVC::zabbix_proxy::process busy %
      - SVC::zabbix_proxy::data gathering process busy %
  - 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 to SVC::Zabbix Proxy::proc Application
    - rename all Processes::$4::$2 to proc::$4::$2 and remove quotes on all those items second key parameter (to allow easy migration from standard "Template App Zabbix Proxy" template)
  - 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
- 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 to SVC::Zabbix Server::proc
  - Graphs:
    - updated SVC::zabbix_server::process busy %
    - new SVC::zabbix_server::preprocessing queue
  - 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
- Service Nginx
  - new template

List of templates:

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 {HOSTNAME} 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.

Copyright (C) 2017-2018 Tomasz Kłoczko [email protected]

This program is free software, distributed under the terms of the GNU General Public License Version 2.

Announcement: development cycle comments

Hi to everyone who is watching this repo :)

I'm going to create devel branch within next 2-3 days and then start committing few changes which I already have queued like:

new php-fpm template
few MIB templates updates
one new metric and graph in zabbix agent template
rewrite Apache template to use master item like it is now in Nginx template.

Up to this moment I will be glad if it will be possible only to review templates, triggers and items descriptions and all README.md files content first.
I'm 100% that it is still a lot to clean on this area :p

Shortly after start work in devel branch hopefully I'll be able to commit tested enough well import_templates script changes. Initially this script will be able to import quickly all templates maintained in this repo. Zabbix has some issues which are kind of obstacles on sharing templates between multiple zabbix servers when when additionally set of those templates are changing.

Without describing now all related details of those issues I think that I can provide procedure of applying such updates in templates allowing to share work results done by many people using additional scripts and few API calls on template update procedure. Here I'm going to use my zapish.inc which is already used in export_templates script.
Nevertheless this will be nothing more than only workaround for some real zabbix issues which sooner or later needs to be solved in zabbix code first. If pressure on solve those issues will be enough hihg because some bunch of people will be sharing some base set of templates I'm sure that Alexey and his team will try to invest some time to address and solve those (already well known) zabbix issues :)
As long as necessary changes will be not implemented straight into zabbix I think that my way of dealing with those issues can provide working solutions of those issues.

If someone already tried to use MIB based templates to assemble monitoring some device please let me know about device type and please submit device template to SNMP Devices/ directory. On submitting such short template with only list of linked other MIB templates please submit result of the commands which I've described on https://github.com/kloczek/zabbix-templates/tree/master/SNMP%20Devices

On sharing those MIB based building blocks templates across many devices monitoring quite important is to verify that results of some changes done in one MIB template on top of one device will have the same or at least similar results in case of using modified/updated MIB template with other device. Different hardware vendors sometimes are embedding in own SNMP agents some changes in code handling even RFCed MIBs.

Happy hacking

kloczek

kloczek / zabbix-templates Goto Github PK