TECHZEN Zenoss User Community ARCHIVE  

DigMonitor Issue

Subject: DigMonitor Issue
Author: [Not Specified]
Posted: 2014-09-04 02:38


I am using DigMonitor for monitoring my DNS server, but it is making me a little confused.
The issue is that I don't really understand the way it works.

The Data Source Configuration is as below:

Cycle Time (seconds): 150
Record Name:
Record Type: A
Severity: Critical
Event Class: /Status/DNS
Timeout (seconds): 10
DNS Server: ${dev/id}
Port: 53

But I'm receiving this Critical alarm:
DNS CRITICAL - 0.007 seconds response time (No ANSWER SECTION found)

Isn't the timeout supposed to be 10 sec Why is it considering as Critical a response time of 0.007 sec
And what makes me even more confused is that the above event is cleared by:

DNS OK - 0.010 seconds response time ( 5 IN CNAME

The 0.010 sec response time seems to be Ok, but 0.007sec is Critical

Can anyone explain me how it is possible Have I made any mistakes in configuration


Subject: 10 seconds timeouts is
Author: Jan Garaj
Posted: 2014-09-04 03:54

10 seconds timeouts is related to "check command" - it must finish in 10 seconds. "check command" can be anything: dig, nslookup, ssh request, .... So this timeout is not related to dig monitor directly in this case

Probably sometimes your DNS server doesn't return answer for dig request:
>DNS CRITICAL - 0.007 seconds response time (No ANSWER SECTION found)

garajj@server:~$ dig

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61221
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 4

; IN A

;; ANSWER SECTION: 900 IN CNAME 300 IN CNAME 43200 IN A 43200 IN A

But it return answers for some requests and then previous critical event is cleared:
> DNS OK - 0.010 seconds response time ( 5 IN CNAME

This check is not about response time, but DNS record must be resolved correctly. Maybe DNSMonitor ZenPack will be better for you. See official doc:

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

< Previous
Zenoss shows "Unknown" for interfaces on secondary router