Add check for DNS resolution

Bug #1793328 reported by Drew Freiberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NRPE Charm
Invalid
Undecided
Unassigned
Nagios Charm
Won't Fix
Low
Unassigned

Bug Description

We should add a check for DNS resolution working in good fashion.

Checking both for timeouts and ability to look up a particular address.

Defaults should probably be warn at 10 seconds, crit at 30 seconds, lookup archive.ubuntu.com.

This will help us identify upstream and cloud DNS issues.

Revision history for this message
Drew Freiberger (afreiberger) wrote :

This could be very noisy on a cloud if enabled by default. Suggest we might want to make it a disabled option by default, but allow for it to be enabled as needed on smaller deploys of the charm, such as nrpe-lxd-service-checks that could get related to something like landscape, nagios, graylog. Or perhaps this could be builtin to the nagios charm itself.

Revision history for this message
Drew Freiberger (afreiberger) wrote :

This is already part of openstack-service-checks. May be invalid for these charms, but should be considered for future nagios charm, as openstack-service-checks should be upstreamed into each individual service's checks eventually.

Changed in nrpe-charm:
status: Confirmed → Invalid
importance: High → Undecided
Andrea Ieri (aieri)
Changed in nagios-charm:
importance: Undecided → Low
status: New → Confirmed
Eric Chen (eric-chen)
Changed in charm-nagios:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.