Project

General

Profile

Feature #8430

Add DNS Resolver status page

Added by Jim Pingle about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
DNS Resolver
Target version:
Start date:
04/04/2018
Due date:
% Done:

50%

Estimated time:

Description

We can fetch some useful status data from unbound using unbound-control -c /var/unbound/unbound.conf <command>, and it would be nice to show some of that to users if we can find a clean way to format it.

At a minimum, dump_infra output should be there so users can have visibility of the internal tracking stats unbound is using about upstream DNS servers. In resolver mode, it lists the roots, in forwarding mode it lists the forwarding servers.

We could also have a page to show the output of dump_cache but that may need some special handling due to its potential size in a busy environment.

There is also some interesting info in stats_noreset but we'd need to pick and choose what to show to avoid information overload.

Potential gotchas: dump_infra will be empty if there have been no DNS queries recently. There are some cases where unbound-control fails to run that still need investigation.

Setting to 2.4.4 for now, but can be moved forward if there is no time for it.

Associated revisions

Revision 4acef976 (diff)
Added by Jim Pingle about 1 year ago

Add a status page for unbound to show the infra cache. Ticket #8430

Revision 23feda19 (diff)
Added by Jim Pingle about 1 year ago

Refinements to status_unbound.php. Ticket #8430

History

#1 Updated by Jim Pingle about 1 year ago

  • % Done changed from 0 to 50

The infra cache stats appear to be good. It might be nice if they updated via ajax but they do not appear to change fast enough for that to matter. All it would do in most cases is show the TTLs decrease in real-time which seems unnecessary.

dump_cache doesn't seem like a good idea the more I think about it. Aside from being tricky to parse bits and pieces out, that level of detail/control seems better to leave at the CLI.

stats_noreset is still viable but it needs more thought about how to present it.

#2 Updated by Jim Pingle about 1 year ago

  • Status changed from New to Resolved

What's there now is enough for this purpose. I haven't yet been able to come up with a good way to represent the data in stats_noreset that seemed like it was worthy of putting in the GUI vs running the command on its own. We can revisit this again in the future if need be.

Also available in: Atom PDF