Zabbix anyone has a working DNS monitor plugin?

[registration_is_lame]

I have found this 2:

Original

https://github.com/Pesticles/Zabbix-Bind9-Statistics-Collection

Mod

https://github.com/remontti/Zabbix-Bind9-Statistics-Collection

Both of them are broken tho
The second guy tried to fix the fist one and left it in half finished status (I talking about the Zabbix 3 templates he is providing I don't want to upgrade to Z5 just because of this).

After installing the template most of the options for the zones are unsupported even tho you can query them fine:

/usr/zabbix4/bin/zabbix_get -s 1.2.3.4 -p10050 -k bind.incounter[NS]

Client side:

#UserParameter=bind.discoverzones,/config/bind-stats-rr.py discoverzones
UserParameter=bind.json,/config/bind-stats-rr.py json
UserParameter=bind.jsonzone[*],/config/bind-stats-rr.py jsonzone -z $1
UserParameter=bind.counter[*],/config/bind-stats-rr.py counter -c $1
UserParameter=bind.zonecounter[*],/config/bind-stats-rr.py zonecounter -z $1 -c $2
UserParameter=bind.zonemaintenancecounter[*],/config/bind-stats-rr.py zonemaintenancecounter -c $1
UserParameter=bind.resolvercounter[*],/config/bind-stats-rr.py resolvercounter -c $1
UserParameter=bind.socketcounter[*],/config/bind-stats-rr.py socketcounter -c $1
UserParameter=bind.incounter[*],/config/bind-stats-rr.py incounter -c $1
UserParameter=bind.outcounter[*],/config/bind-stats-rr.py outcounter -c $1
UserParameter=bind.memory[*],/config/bind-stats-rr.py memory -c $1
UserParameter=bind.cache[*],/config/bind-stats-rr.py cache -c $1

So I have deleted the template from the Zabbix server and manually created items but it does not make any sense and here is why:



These numbers will just grow forever. I need the query stats per minute properly.
Yeah I know I could just go back to Munin because there is a working out of the box Bind plugin for it but why when I have Zabbix installed everywhere.

[registration_is_lame]

bump bump bump

[registration_is_lame]

Now that you have said that I have realized that the original templates what I mentioned that it does not work turned out to be doing something. I just need to hammer the DNS server with queries to be able to see it.


So with normal amount of queries it wont show anything it needed to be flooded. Anyone has a better DNS monitor plugin for Zabbix maybe???

[eithor]

Make sure that you use float instead of integer when you use "change per second", or it will round down to 0.

[cyber]

If numbers grow forever and you need "per minute", then use preprocessing for item. "Change per second" is your friend in this case.

https://www.zabbix.com/documentation/current/manual/config/items/preprocessing

Change per second

Calculate the value change (difference between the current and previous value) speed per second. Evaluated as (value-prev_value)/(time-prev_time), where value - current value; prev_value - previously received value; time - current timestamp; prev_time - timestamp of previous value. This setting is extremely useful to get speed per second for a constantly growing value. If the current value is smaller than the previous value, Zabbix discards that difference (stores nothing) and waits for another value. This helps to work correctly with, for instance, a wrapping (overflow) of 32-bit SNMP counters. Note: As this calculation may produce floating-point numbers, it is recommended to set the 'Type of information' to Numeric (float), even if the incoming raw values are integers. This is especially relevant for small numbers where the decimal part matters. If the floating-point values are large and may exceed the 'float' field length in which case the entire value may be lost, it is actually suggested to use Numeric (unsigned) and thus trim only the decimal part. Only one change operation per item is allowed. If you mark the Custom on fail checkbox, the item will not become unsupported in case of failed preprocessing step and it is possible to specify custom error handling options: either to discard the value, set a specified value, or set a specified error message.