# Monitor the compiled version of unbound with munin

**URL:** <https://discourse.pi-hole.net/t/monitor-the-compiled-version-of-unbound-with-munin/20182>\
**Category:** Customizing Pi-hole\
**Created:** [May 28, 2019, 10:05am UTC](https://discourse.pi-hole.net/t/monitor-the-compiled-version-of-unbound-with-munin/20182 "2019-05-28T10:05:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpgpi250](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jpgpi250/32/286_2.png) [@jpgpi250](https://discourse.pi-hole.net/u/jpgpi250)\
**Post date:** [May 28, 2019, 10:05am UTC](https://discourse.pi-hole.net/t/monitor-the-compiled-version-of-unbound-with-munin/20182/1 "2019-05-28T10:05:03Z")

</div>

For this to work, you need to compile unbound from source, explained [here](https://discourse.pi-hole.net/t/compiling-unbound-from-source-getting-unbound-to-work-with-dns-over-tls/19017/2).

My unbound configuration files (without the additional munin configuration) are listed [here](https://discourse.pi-hole.net/t/anyone-using-knot-resolver/19750/29).

The installation notes (README) and script can be found [here](https://github.com/jpgpi250/munin). You need to make some modifications to the install script to reflect the actual IP and domain of your system, so read the README first.

Your system needs to be running unbound and munin for several days / weeks, before the resulting graphs become meaningful.

result:

 ![munin](https://discourse.pi-hole.net/uploads/default/original/2X/8/8de73b47e8fc280e4cb29f987160e7fafd1d9284.png)

 ![image](https://discourse.pi-hole.net/uploads/default/original/2X/a/aa3628e43430a9f9b25aa904197e5250ce9feee4.png)