Giter Site home page Giter Site logo

community-templates's Introduction

Zabbix public templates

A place for community driven integrations with Zabbix

Template Repository Template Repository

This repository is dedicated to templates that are created and maintained by Zabbix community.

How to use templates from this repository?

  • Download and import a template into the supported Zabbix version.
  • Configure the template according to the configuration requirements
  • Configure a host with template

How to Collaborate?

  • Fix and report bugs
  • Improve template documentation
  • Review and discuss templates and feature proposals
  • Answer questions and discuss in GitHub issues

How to contribute a new template

  • Read template guidelines
  • Review template structure
  • Open a pull request with a template for the correct version
  • Be ready to discuss your pull request

Templates

community-templates's People

Contributors

abakaldin avatar actions-user avatar anilantari avatar aquilospiritus avatar deepdreamer89 avatar diasdmhub avatar gianlucaromito avatar gidai7ja avatar gijack avatar gitbock avatar guerlielton avatar h3c-bmc avatar hlovdal avatar jaxom99 avatar lmawizard avatar luanvso avatar marco-ostaska avatar mariuskarotkis avatar massimilianopasquini97 avatar onlycrab avatar oscar120584 avatar packetsar avatar patxiandueza avatar rogertheunicornhive avatar saigets avatar svalentin1984 avatar tbblake avatar thiagomdiniz avatar tweiers avatar vermiz avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

community-templates's Issues

template_sugon_rackserver_monitor issue

We just deployed Zabbix 6.0 in our environment, and we are using I610-G20 and I620-G20 of SUGON server, if possible to modify this template fix for it?
We just tried this template, but shows 'No Such Object available on this agent at this OID'.

Would you please help for that?

template_lvm_cache is missing script, userparameters and sudoers-file

In Readme of template_lvm_cache, the user is instructed to

  • Put file lvmcache.conf to /etc/zabbix/zabbix_agent.d/
  • Put file sudoers_lvmcache to /etc/sudoers.d/ (you need sudo program installed)
  • Put file vmcache to /etc/zabbix/scripts/. Then you can execut this file and test. This script produces JSON output.

But none of those files are included in the community-templates/tree/main/Operating_Systems/Linux/template_lvm_cache/* repo.

What interface should we add for a kubernetes node

When using zabbix-kube-prom template, the docs says:

"Create or import a host identifying your Kubernetes cluster where Prometheus is deployed."

What interface type we should select to add the host?
I am not expecting it should be agent, as it is not required to run agent on the cluster.

I have selected the macro {$PROM.API.URL} and pointed to the Prometheus API URL within the cluster. But it is not showing any metrics.

HashiCorp templates not accessible anymore

Hi,

A few weeks ago I was able to access the HashiCorp Nomad and Consul templates that were available on share.zabbix.com. If I try to visit them now, I get a 404. Could you please bring back these templates?

Chris

Contribute with a New Template

I created a new template to monitor Extreme Wireless access points, i want to share this template with the community but i dont know how to do it.

Bellow its the exported template:

`

zabbix_export:
version: '6.0'
date: '2022-03-01T18:11:57Z'
groups:
-
uuid: 7df96b18c230490a9a0a9e2307226338
name: Templates
-
uuid: 36bff6c29af64692839d077febfc7079
name: 'Templates/Network devices'
templates:
-
uuid: 13a782b8685e4781afc5c7d4f3d84094
template: 'Template Extreme Wing AP'
name: 'Template Extreme Wing AP'
templates:
-
name: 'Template Module EtherLike-MIB SNMP'
-
name: 'Template Module Generic SNMP'
-
name: 'Template Module Interfaces SNMPv2'
groups:
-
name: Templates
-
name: 'Templates/Network devices'
items:
-
uuid: 82ace776068f4ef38a079baa2dff5e8f
name: 'CPU Utilization'
type: SNMP_AGENT
snmp_oid: .1.3.6.1.4.1.388.50.1.4.2.2.2.1.0
key: cpu.utilization
delay: 2m
history: 15d
trends: 90d
value_type: FLOAT
units: '%'
description: '10 times the average cpu load over the last minute (2 => .2 % cpu load)'
preprocessing:
-
type: MULTIPLIER
parameters:
- '0.1'
tags:
-
tag: Application
value: Status
-
uuid: 7c1a2ca592ac45f9bf936e9337b326da
name: 'Free Ram Memory'
type: SNMP_AGENT
snmp_oid: .1.3.6.1.4.1.388.50.1.4.2.2.2.3.0
key: ram.free
delay: 2m
history: 15d
trends: 90d
value_type: FLOAT
units: '%'
description: '10 times the percentage of currently free RAM (687 => 68,7 % free memory)'
preprocessing:
-
type: MULTIPLIER
parameters:
- '0.1'
tags:
-
tag: Application
value: Status
discovery_rules:
-
uuid: 9e22f41724ba4b458eb3ab5f257fa3f3
name: 'AP Discovery'
type: SNMP_AGENT
snmp_oid: 'discovery[{#APNAME},.1.3.6.1.4.1.388.50.1.4.2.25.1.1.1.9]'
key: apdiscovery
delay: 5h
item_prototypes:
-
uuid: 9f925fe64a9d4ac887e1c82489aefe6a
name: 'Connected Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.1.1.1.4.{#SNMPINDEX}'
key: ap.connectedclients
delay: 5m
history: 15d
trends: 90d
tags:
-
tag: Application
value: Clients
-
uuid: fe064f5a147648d89d708ac77c6ed7b7
name: 'Fault Detected'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.1.1.1.2.{#SNMPINDEX}'
key: ap.fault.detected
delay: 2m
history: 15d
trends: '0'
value_type: CHAR
tags:
-
tag: Application
value: Status
-
uuid: 8b8ebca012a843748d27674e1f674f6e
name: 'Last Cal Time'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.1.1.1.5.{#SNMPINDEX}'
key: ap.lastcalltime
delay: 5m
trends: '0'
value_type: CHAR
description: 'Last Smart-RF Calibration time on the AP'
tags:
-
tag: Application
value: Status
-
uuid: 89956e24e61c48b28a67b55354edb6a5
name: 'Number of Radios'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.1.1.1.3.{#SNMPINDEX}'
key: ap.numradios
delay: 3h
history: 15d
trends: 90d
tags:
-
tag: Application
value: Inventory
-
uuid: 5266fb642916482dab5bd86a57f01d79
name: 'Device Discovery'
type: SNMP_AGENT
snmp_oid: 'discovery[{#DEVICENAME},.1.3.6.1.4.1.388.50.1.4.2.1.1.3]'
key: device.discovery
delay: 5h
item_prototypes:
-
uuid: ff41fd9109d94e17ae412ef943a4331d
name: 'Device Model'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.1.1.2.{#SNMPINDEX}'
key: device.model
delay: 3h
history: 15d
trends: '0'
value_type: CHAR
tags:
-
tag: Application
value: Inventory
-
uuid: 0e1279352dc34717a145fd414a53d277
name: 'Online Status'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.1.1.7.{#SNMPINDEX}'
key: device.onlinestatus
delay: 5m
history: 15d
trends: '0'
value_type: CHAR
tags:
-
tag: Application
value: Status
-
uuid: 1f44afcdd45a409993fde0d988d83d8f
name: 'Serial Number'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.1.1.5.{#SNMPINDEX}'
key: device.serialnumber
delay: 3h
history: 15d
trends: '0'
value_type: CHAR
tags:
-
tag: Application
value: Inventory
-
uuid: 16f97762026f4dd7bbbe0946d78ef30d
name: 'Device Version'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.1.1.4.{#SNMPINDEX}'
key: device.version
delay: 3h
history: 15d
trends: '0'
value_type: CHAR
tags:
-
tag: Application
value: Inventory
-
uuid: 94e85699c0a94b62a72261ccaca60989
name: 'Radios Discovery'
type: SNMP_AGENT
snmp_oid: 'discovery[{#RADIONAME},.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.3,{#RADIOALIAS},.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.5]'
key: radios.discovery
delay: 5h
item_prototypes:
-
uuid: ba4cbe114afc4811aa415c2b1f87c440
name: '{#RADIONAME}:{#RADIOALIAS} 11a Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.26.{#SNMPINDEX}'
key: 'radio.11aclients.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
description: 'Number of 11a clients'
tags:
-
tag: Application
value: Clients
-
tag: Application
value: Radios
-
uuid: 0ea1634bc1c04238b79ca124c37b477c
name: '{#RADIONAME}:{#RADIOALIAS} 11an Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.27.{#SNMPINDEX}'
key: 'radio.11anclients.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
description: 'Number of 11an clients'
tags:
-
tag: Application
value: Clients
-
tag: Application
value: Radios
-
uuid: 09c3a2d134644e8da7eddc4f73e45cac
name: '{#RADIONAME}:{#RADIOALIAS} 11b Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.23.{#SNMPINDEX}'
key: 'radio.11bclients.[{#RADIONAME}]'
delay: 5m
description: 'Number of 11b connected clients'
tags:
-
tag: Application
value: Clients
-
tag: Application
value: Radios
-
uuid: c39f74e76b0a45e096da8cd3237e8e06
name: '{#RADIONAME}:{#RADIOALIAS} 11bg Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.24.{#SNMPINDEX}'
key: 'radio.11bgclients.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
description: 'Number of 11bg clients'
tags:
-
tag: Application
value: Clients
-
tag: Application
value: Radios
-
uuid: 38090621897946be8011eaabbd813d49
name: '{#RADIONAME}:{#RADIOALIAS} 11bgn Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.25.{#SNMPINDEX}'
key: 'radio.11bgnclients.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
description: 'Number of 11bgn clients'
tags:
-
tag: Application
value: Clients
-
tag: Application
value: Radios
-
uuid: b8929fb8e366410fbad2ee96c9de69d8
name: '{#RADIONAME}:{#RADIOALIAS} Clients'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.15.{#SNMPINDEX}'
key: 'radio.clients.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
description: 'Connected clients'
tags:
-
tag: Application
value: Radios
-
uuid: 7ebebf5bef9e4e17951b78f231c035d7
name: '{#RADIONAME}:{#RADIOALIAS} Config Channel'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.11.{#SNMPINDEX}'
key: 'radio.configchannel.[{#RADIONAME}]'
delay: 10m
history: 15d
trends: '0'
value_type: CHAR
description: |
Configured Channel
smt = Smart RF
tags:
-
tag: Application
value: Radios
-
uuid: 6db62783223046e0b41b2c11de6c9565
name: '{#RADIONAME}:{#RADIOALIAS} Config Power'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.13.{#SNMPINDEX}'
key: 'radio.configpower.[{#RADIONAME}]'
delay: 10m
history: 15d
trends: '0'
value_type: CHAR
description: |
Configured Power
smt = Smart RF
tags:
-
tag: Application
value: Radios
-
uuid: 163b6c739e0f466fbb413da15a19efb0
name: '{#RADIONAME}:{#RADIOALIAS} Current Channel'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.10.{#SNMPINDEX}'
key: 'radio.curchannel.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: '0'
value_type: CHAR
description: 'Current utilized channel'
tags:
-
tag: Application
value: Radios
-
uuid: f93d8e94669743a3b63ed63483d2f4d9
name: '{#RADIONAME}:{#RADIOALIAS} Current power'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.12.{#SNMPINDEX}'
key: 'radio.curpower.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 30d
units: dBm
description: 'Current power level'
tags:
-
tag: Application
value: Radios
-
uuid: d510d0ea633d481a99085b886537ff6e
name: '{#RADIONAME}:{#RADIOALIAS} Error Rate'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.20.{#SNMPINDEX}'
key: 'radio.errorrate.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: '%'
description: 'Ratio of errors to rx-packets in percentage'
tags:
-
tag: Application
value: Radios
-
uuid: 07620305a6414581a630aaa585d91e74
name: '{#RADIONAME}:{#RADIOALIAS} Max User Rate'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.14.{#SNMPINDEX}'
key: 'radio.maxuserrate.[{#RADIONAME}]'
delay: 1h
history: 7d
trends: '0'
units: kbps
description: 'Theoretic maximum user-level data rate'
tags:
-
tag: Application
value: Radios
-
uuid: e96f42280af844de961bde985dd26957
name: '{#RADIONAME}:{#RADIOALIAS} Noise'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.16.{#SNMPINDEX}'
key: 'radio.noise.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
value_type: FLOAT
units: dbm
description: 'Noise level in units of dbm'
tags:
-
tag: Application
value: Radios
-
uuid: 349a9f0ccf35422c8bb38278d1c18bab
name: '{#RADIONAME}:{#RADIOALIAS} Radio Protocol'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.16.{#SNMPINDEX}'
key: 'radio.protocol.[{#RADIONAME}]'
delay: 1h
history: 7d
trends: '0'
tags:
-
tag: Application
value: Radios
-
uuid: 6333954998a2473481a797ed86c7a031
name: '{#RADIONAME}:{#RADIOALIAS} Quality Index'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.21.{#SNMPINDEX}'
key: 'radio.quality.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: '%'
description: |
RF quality Index
Measure the quality of the medium in percentage. It is a
function of average retries and error rate. Its range is from
0-100. Typically:
-1: no data available ( e.g. radio is not in wlan operation
mode )
0-20: very poor quality
20-40: poor quality
40-60: average quality
60-100: good quality
tags:
-
tag: Application
value: Radios
-
uuid: f7fb96538f7c4425bd7a213d410e2d36
name: '{#RADIONAME}:{#RADIOALIAS} Rx Bps'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.14.{#SNMPINDEX}'
key: 'radio.rxbps.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: bps
description: 'User data receive rate'
tags:
-
tag: Application
value: Radios
-
uuid: 7f7cd09342c04b8ba12292893478d552
name: '{#RADIONAME}:{#RADIOALIAS} Rx Bytes'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.7.{#SNMPINDEX}'
key: 'radio.rxbytes.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
value_type: FLOAT
units: B
description: 'Number of data bytes received from clients to radio'
tags:
-
tag: Application
value: Radios
-
uuid: a701ca7f1d2245e881a17f7495eccd81
name: '{#RADIONAME}:{#RADIOALIAS} Rx Errors'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.11.{#SNMPINDEX}'
key: 'radio.rxerrors.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
value_type: FLOAT
description: 'Number of packets of data received with errors'
tags:
-
tag: Application
value: Radios
-
uuid: fd9c5f41b838449b8928af898c123083
name: '{#RADIONAME}:{#RADIOALIAS} Rx Rate'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.19.{#SNMPINDEX}'
key: 'radio.rxrate.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: Mbps
description: 'The effective phy-layer receive rate'
tags:
-
tag: Application
value: Radios
-
uuid: 55d5931affbd4e689ea65d17405cc12d
name: '{#RADIONAME}:{#RADIOALIAS} Signal'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.15.{#SNMPINDEX}'
key: 'radio.signal.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
value_type: FLOAT
units: dbm
description: 'Signal strength in units of dbm'
tags:
-
tag: Application
value: Radios
-
uuid: 2a5396b2105a4b728faf2841e409c040
name: '{#RADIONAME}:{#RADIOALIAS} Signal to Noise'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.17.{#SNMPINDEX}'
key: 'radio.snr.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: db
description: 'Signal to noise ratio in units of db'
tags:
-
tag: Application
value: Radios
-
uuid: d2c7e8b4f9cd49789e699da6161acec3
name: '{#RADIONAME}:{#RADIOALIAS} Status'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.9.{#SNMPINDEX}'
key: 'radio.status.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: '0'
value_type: CHAR
description: 'Radio state'
tags:
-
tag: Application
value: Radios
-
uuid: 4843f9188322421c97117a41210e0eab
name: '{#RADIONAME}:{#RADIOALIAS} Traffic Utilization Index'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.12.{#SNMPINDEX}'
key: 'radio.tindex.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
description: |
Traffic Utilization Index
Measures the efficiency the medium under consideration
is used. It is the percentage of the current data throughput
over the theoretical data rate limit, which is derived
the current maximum physical rate configured over the medium
based on past empirical data. This index could assist end user
in site planning and expansion. The numerical value might be
further classified as:
-1: no data available ( e.g. radio is not in wlan operation
mode )
0-20 : very low utilization
20-40: low utilization
40-60: moderate utilization
60 and above: high utilization
tags:
-
tag: Application
value: Radios
-
uuid: afed6ff5f7f44bed9e8d517614fe5383
name: '{#RADIONAME}:{#RADIOALIAS} Tx Bps'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.13.{#SNMPINDEX}'
key: 'radio.txbps.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: kbps
description: 'User data transmit rate'
tags:
-
tag: Application
value: Radios
-
uuid: 23f180db0e934d94baf5c2085172f89b
name: '{#RADIONAME}:{#RADIOALIAS} Tx Bytes'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.6.{#SNMPINDEX}'
key: 'radio.txbytes.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
value_type: FLOAT
units: B
description: 'Number of data bytes transmitted from radio to clients'
tags:
-
tag: Application
value: Radios
-
uuid: 263dddd2d6494de7802f9d29049323f0
name: '{#RADIONAME}:{#RADIOALIAS} Tx Dropped'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.10.{#SNMPINDEX}'
key: 'radio.txdropped.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
value_type: FLOAT
description: 'Number of packets of data dropped on transmission'
tags:
-
tag: Application
value: Radios
-
uuid: 0b431df6bcb5405d99245541b8b47a0c
name: '{#RADIONAME}:{#RADIOALIAS} Tx Rate'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.10.1.1.18.{#SNMPINDEX}'
key: 'radio.txrate.[{#RADIONAME}]'
delay: 5m
history: 15d
trends: 90d
units: Mbps
description: 'The effective phy-layer transmit rate'
-
uuid: 37f8a4a45276410b852ed68b4bc0401c
name: '{#RADIONAME}:{#RADIOALIAS} Radio Type'
type: SNMP_AGENT
snmp_oid: '.1.3.6.1.4.1.388.50.1.4.2.25.9.1.1.5.{#SNMPINDEX}'
key: 'radio.type.[{#RADIONAME}]'
delay: 1h
history: 15d
trends: '0'
value_type: CHAR
tags:
-
tag: Application
value: Radios
macros:
-
macro: '{$IF_ERRORS_WARN}'
value: '1000'
`

SNMP Fortinet Devices - incorrent handling of Connections item

Zabbix template SNMP Fortinet Devices https://github.com/zabbix/community-templates/tree/main/Network_Devices/Fortigate/template_fortigate_snmp appears to have a bug in handling the Connections item - the Current Connections item (OID .1.3.6.1.4.1.12356.101.4.1.8.0) is handled as a counter, with "KC" unit (meaning thousand connections?), but an inspection of the actual value returned on our FortiGate 60F with 6.4.8 firmware indicates that the value actually is a gauge, returning the current connection count without any scaling.

Suggested fix:

Attached is the export of our modified template. We are using Zabbix 5.0, so I cannot check the Zabbix 5.4 and 6.0 versions of the template (in YAML format), but reading them, I think they have the same configuration - behavior of Connections Count.

As the template in GH is in compact, single-line XML, hard to read and show differences, here is the diff of formatted versions of the template with xmlstarlet fo:

--- template_fortigate_snmp-fmt.xml     2022-04-11 17:05:24.993615084 +0200
+++ zbx_export_templates-fmt.xml        2022-04-11 16:54:33.657009129 +0200
@@ -75,18 +46,12 @@
           <snmp_oid>.1.3.6.1.4.1.12356.101.4.1.8.0</snmp_oid>
           <key>fortinetCurrentConnections</key>
           <delay>60</delay>
-          <units>KC</units>
+          <units>Conn</units>
           <applications>
             <application>
               <name>Fortinet Performance</name>
             </application>
           </applications>
-          <preprocessing>
-            <step>
-              <type>CHANGE_PER_SECOND</type>
-              <params/>
-            </step>
-          </preprocessing>
         </item>
         <item>
           <name>Current CPU Util</name>

The files (with some additional differences) are attached:
Original file, formatd: template_fortigate_snmp-fmt.xml.gz
Modified file, formated: zbx_export_templates-fmt.xml.gz

template_bind_stat not working .

My agent is as follows ;

$# zabbix_agent2 -version
zabbix_agent2 (Zabbix) 5.4.12

I get this error message after adding the bind.conf file .

2022/04/11 16:14:24.868061 Starting Zabbix Agent 2 (5.4.12)
2022/04/11 16:14:24.868666 OpenSSL library (OpenSSL 1.1.1  11 Sep 2018) initialized
2022/04/11 16:14:24.871519 using configuration file: /etc/zabbix/zabbix_agent2.conf
2022/04/11 16:14:24.871654 cannot initialize user parameters: cannot add user parameter "bind.queries.in[],curl http://127.0.0.1:8053/ 2>/dev/null | xml2 | grep -A1 "/statistics/server/counters/counter/@name=$1$" | tail -1 | cut -d= -f2": syntax error

template_synology_diskstation Disk size/usage/percentage incorrect

HI
This script incorrectly pulls the correct sizes from my Synology NAS. On a 60TB disk named /volume1it only reports 7TB. However if I SNMPWALK using the OID from Synology for disk info, I get the correct raw values:

snmpwalk -v2c -c public ....* .1.3.6.1.4.1.6574.3
iso.3.6.1.4.1.6574.3.1.1.1.0 = INTEGER: 0
iso.3.6.1.4.1.6574.3.1.1.2.0 = STRING: "Volume 1"
iso.3.6.1.4.1.6574.3.1.1.3.0 = INTEGER: 1
iso.3.6.1.4.1.6574.3.1.1.4.0 = Counter64: 2423850156032
iso.3.6.1.4.1.6574.3.1.1.5.0 = Counter64: 65697681559552

The script seems to be going a long way round when the values are presented on this ID in Bytes. Could you please correct this?

template_huawei_oceanstore/5.4/huawei_get_state.py

[Good afternoon! Could you add to the repository huawei_get_state.py the script, otherwise it is missing
https://github.com/zabbix/community-templates/tree/main/Storage_Devices/Huawei/template_huawei_oceanstore/5.4

Pihole API Template for Zabbix 6 -

On your DNS Query graph I wonder if there is missing data. I would almost expect to see a type for queries that were blocked, which would be in line with the graph on the Pihole admin console. I do not see a graph for this data. Could this be amended?

Screenshot 2022-05-04 125337
Screenshot 2022-05-04 125407

This github repository is not searchable, intuitive, or easy to use

Unlike share.zabbix.com, this repo is not searchable. This is an important feature on share.zabbix.com that allows users to find templates for their devices. This repo is not easy to use if you want to add a template, not all of us are developers. The layout of template name/version/release is cumbersome and difficult.

Suggestions:

  • ditch this idea and improve zabbix share instead
  • index this github repo on search engines
  • enable the github wiki with a searchable index

cisco total

import template error
Не удалось найти элемент данных "ciscoMemoryPoolFree[{#SNMPINDEX}]" у "Cisco Total", используемый в прототипе графиков "{#SNMPINDEX} Memory Free" правила обнаружения "Cisco memory pool discovery" у "Cisco Total".

Template PiHole 6.0

Hello, in the PiHole template (6.0), the items below are returning different values from the API, as can be seen in the photos.

ads_blocked_today

api pihole -> https://i.ibb.co/86DhdS1/ad-today-pi.png
zabbix -> https://i.ibb.co/j3HNPND/ad-today-zabbix.png

dns_queries_today

api pihole -> https://i.ibb.co/jGy29Rc/dns-today-pi.png
zabbix -> https://i.ibb.co/ZKXbr2R/dns-today-zabbix.png

dns_queries_all_types

api pihole -> https://i.ibb.co/c2d2dCq/dns-all-pi.png
zabbix -> https://i.ibb.co/XJnxy03/dns-all-zabbix.png

Проблема с локализацией

Locale for language "en_US" is not found on the web server. Tried to set: en_US, en_US.utf8, en_US.UTF-8, en_US.iso885915, en_US.ISO8859-1, en_US.ISO8859-2, en_US.ISO8859-4, en_US.ISO8859-5, en_US.ISO8859-15, en_US.ISO8859-13, en_US.CP1131, en_US.CP1251, en_US.CP1251, en_US.CP949, en_US.KOI8-U, en_US.US-ASCII, en_US.eucKR, en_US.eucJP, en_US.SJIS, en_US.GB18030, en_US.GB2312, en_US.GBK, en_US.eucCN, en_US.Big5HKSCS, en_US.Big5, en_US.armscii8, en_US.cp1251, en_US.eucjp, en_US.euckr, en_US.euctw, en_US.gb18030, en_US.gbk, en_US.koi8r, en_US.tcvn. Unable to translate Zabbix interface.
image
image

template_veeam_agents_for_microsoft_windows 5.4 doesn't log all the time

Hi,

I'm running Zabbix Server 5.4.12 with Zabbix Agent 2 5.4.12 in active mode running on my hosts.
Hosts are running Veeam Agent for Microsoft Windows Free release 5.0.3.4708.
Every Veeam Agent is configured to do backup just once a week (this is because on the host there aren't any data to save, full image backup is just for fast restore of operating system).
Zabbix Server discontinuosly reports information about item VeeamAgent_EventLog_JobResult within Zabbix Global view Dashboard on Problems widget, for some hosts I can see the record on the Zabbix Dashboard for some other host I have never seen any alert.
If, for every hosts, I check historical data for item VeeamAgent_EventLog_JobResult I can see results for every weekly backup job.

Is this behaviour normal?

I just wouldlike to see on Zabbix Dashboard every result of item VeeamAgent_EventLog_JobResult for every monitored hosts.

Thanks in advance to anyone could help me.

RS

Can't run logstash script.

  1. Added template logstash/6.0/ into Zabbix6

  2. Then follows "fredprod" guide.

  3. Tried with python2 and python3

  4. Using logstash-v6x.py from the linked guide.

When i run the script locally on a logstash-server i get the following error:
And i can see the same result in zabbix GUI "logstash check"

Traceback (most recent call last): File "./logstash.py", line 112, in <module> ret = LogstashServer().run() File "/usr/lib/python2.7/site-packages/protobix/sampleprobe.py", line 281, in run self.zbx_config = self._init_config() File "/usr/lib/python2.7/site-packages/protobix/sampleprobe.py", line 204, in _init_config zbx_config = ZabbixAgentConfig(self.options.config_file) File "/usr/lib/python2.7/site-packages/protobix/zabbixagentconfig.py", line 56, in __init__ tmp_config = configobj.ConfigObj(config_file, list_values=False) File "/usr/lib/python2.7/site-packages/configobj.py", line 1229, in __init__ self._load(infile, configspec) File "/usr/lib/python2.7/site-packages/configobj.py", line 1318, in _load raise error configobj.DuplicateError: Duplicate keyword name at line 16.

Why no GPL licenses?

In the guidelines I found the following:

Licensing

All community templates are published under the MIT license. Third-party licenses, even the compatible ones (for example, GPL v2/v3) are not accepted.

Furthermore, the repo is under MIT, but Zabbix itself is under GPL. I can't quite understand this step backwards in licensing.

Would it be possible to offer another repo for GPL licensed community templates?

I would love to help the community with my templates, but then also under the condition that my contribution remains free.

2 Microsoft SQL templates appear to be missing information

template_app_ms_sql_database_discovery_(lld)
references key: windowsdb.discovery
template_app_ms_sql_instance_discovery_(lld)
references key: windowssqlinstances.discovery

These are not agent or agent2 built-in keys. Therefore there must have been additional scripts or at least user parameters that would need to be defined. These templates should be marked as incomplete, or the additional information added.

I tried searching for more info using:

Json Path not working

Json Path not working, give error in Test all steps but individual test not problem.
cannot extract value from json by path "$.lastName": cannot parse as a valid JSON object: invalid object format, expected opening character '{' or '[' at: 'John'
for the second parameter for prossecing
but Json format is okay

{
"firstName": "John",
"lastName" : "doe",
"age" : 26,
"address" : {
"streetAddress": "naist street",
"city" : "Nara",
"postalCode" : "630-0192"
},
"phoneNumbers": [
{
"type" : "iPhone",
"number": "0123-4567-8888"
},
{
"type" : "home",
"number": "0123-4567-8910"
}
]
}

template_synology_diskstation wrong volume size calculated

The disksize is calculated with a fixed multiplier of 4096, however, the value can be also different as it is with my unit.
Checking the value for hrStorageAllocationUnits with mibbrowser shows 16384 instead of 4096.
Another volume on the unit has 4096 for hrStorageAllocationUnits.
My suggestion would be to calculate with the value of hrStorageAllocationUnits.

Below a filtered view of the snmp information.

"hrStorageIndex","hrStorageType","hrStorageDescr","hrStorageAllocationUnits","hrStorageSize","hrStorageUsed","hrStorageAllocationFailures","Index Value"
"55",".1.3.6.1.2.1.25.2.1.4","/volume1","16384","1170658963","864524997",""," 55"
"56",".1.3.6.1.2.1.25.2.1.4","/volumeUSB2/usbshare","4096","360501858","314950992",""," 56"
"61",".1.3.6.1.2.1.25.2.1.4","/volumeUSB1/usbshare","4096","720787053","382743615",""," 61"
"63",".1.3.6.1.2.1.25.2.1.4","/volume2","4096","54861497","1497091",""," 63"

Template 'macOS Content Cache' does not create graphs.

The RemoteCommands are executed, but the values received are not transferred to the graphic.

The output according to the test:

{"name":"status","result":{"Activated":true,"Active":true,"ActualCacheUsed":1781398204,"CacheDetails":{"iCloud":150581984,"iOS Software":1758456112},"CacheFree":19506686976,"CacheLimit":994000000000,"CacheStatus":"OK","CacheUsed":1909038096,"MaxCachePressureLast1Hour":0,"Parents":[],"Peers":[],"PersonalCacheFree":19506686976,"PersonalCacheLimit":994000000000,"PersonalCacheUsed":150581984,"Port":52923,"PrivateAddresses":["192.168.178.204"],"PublicAddress":"89.1.213.19","RegistrationStatus":1,"RestrictedMedia":false,"ServerGUID":"ED91D0ED-04B5-4192-B972-87099F46079A","StartupStatus":"OK","TetheratorStatus":1,"TotalBytesAreSince":"2022-03-18 13:09:06 +0000","TotalBytesDropped":0,"TotalBytesImported":5667338,"TotalBytesReturnedToChildren":0,"TotalBytesReturnedToClients":1775744901,"TotalBytesReturnedToPeers":0,"TotalBytesStoredFromOrigin":1775730866,"TotalBytesStoredFromParents":0,"TotalBytesStoredFromPeers":0}}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.