Reporting on concurrent recursive clients

[ Edited ]
Posts: 82
4370     6

Since 7.3.200 & newer versions, it is possible to redirect member syslog to the reporting appliance.

The direct application for reporting on concurrent recursive clients
named syslog example:
2016-06-21 09:50:04 CEST,"daemon","INFO","named[1583]","Recursion client quota: used/max/soft-limit/s-over/hard-limit/h-over/low-pri = 0/4/0/0/1000/0/0" 
1) Enable Syslog redirection & syslog index in reporting properties
Capture d’écran 2016-06-21 à 22.37.53.png
2) Field extraction
Add a field extration for the sourcetype ib:syslog
Capture d’écran 2016-06-21 à 22.49.19.png
3) Testing Field Extraction
index="ib_syslog" "Recursion client quota"
 Capture d’écran 2016-06-21 à 22.26.12.png
4) Statistics
index=ib_syslog "Recursion client quota" | timechart avg(used) as used ,avg(max) as max ,avg(soft_limit) as soft_limit ,avg(s_over) as s_over ,avg(hard_limit) as hard_limit ,avg(h_over) as h_over ,avg(low_pri) as low_pri
5) Graphing
Capture d’écran 2016-11-16 à 09.28.37.png
Check out our new Tech docs website at for latest documentation on Infoblox products.

Re: Reporting on concurrent recursive clients

Posts: 292
4371     6

Great stuff, I had to do this years ago with Cacti and BIND which called a script to execute "rndc status" every few minutes and pulled out the recursive client usage. This looks like a much better way to do it! :-)

Paul Roberts
PCN (UK) Ltd

All opinions expressed are my own and not representative of PCN Inc./PCN (UK) Ltd. E&OE
Showing results for 
Search instead for 
Did you mean: 

Recommended for You