Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/letsencrypt/unbound_exporter
A Prometheus exporter for Unbound.
https://github.com/letsencrypt/unbound_exporter
Last synced: 4 days ago
JSON representation
A Prometheus exporter for Unbound.
- Host: GitHub
- URL: https://github.com/letsencrypt/unbound_exporter
- Owner: letsencrypt
- License: apache-2.0
- Created: 2017-01-09T08:18:02.000Z (almost 8 years ago)
- Default Branch: main
- Last Pushed: 2024-05-20T17:55:28.000Z (6 months ago)
- Last Synced: 2024-11-05T21:45:14.969Z (7 days ago)
- Language: Go
- Size: 62.5 KB
- Stars: 178
- Watchers: 17
- Forks: 80
- Open Issues: 19
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Prometheus Unbound exporter
This repository provides code for a simple Prometheus metrics exporter
for [the Unbound DNS resolver](https://unbound.net/). This exporter
connects to Unbounds TLS control socket and sends the `stats_noreset`
command, causing Unbound to return metrics as key-value pairs. The
metrics exporter converts Unbound metric names to Prometheus metric
names and labels by using a set of regular expressions.
- - - -
# Prerequisites
Go 1.20 or above is required.
# Installation
go install github.com/letsencrypt/unbound_exporter@latest
This will install the binary in `$GOBIN`, or `$HOME/go/bin` if
`$GOBIN` is unset.
# Updating dependencies
```
go get -u
go mod tidy
```
- - - -
# Usage - Unix socket
The simplest way to run unbound_exporter is on the same machine as your Unbound instance, connecting via a Unix socket. First, make sure you have this in your unbound.conf:
remote-control:
control-enable: yes
control-interface: /run/unbound.ctl
Then, arrange to run this on the same machine:
unbound_exporter -unbound.ca "" -unbound.cert "" -unbound.host "unix:///run/unbound.ctl"
Metrics will be exported under /metrics, on port 9167, on all interfaces.
$ curl 127.0.0.1:9167/metrics | grep '^unbound_up'
unbound_up 1
# Usage - TLS
The more complicated way to run unbound_exporter is to configure unbound's control-interface with a TLS certificate from a private CA, and run unbound_exporter on a separate host. This is more of a hassle because you have to keep the certificate up to date and distribute the private CA to the host that unbound_exporter runs on.
See https://unbound.docs.nlnetlabs.nl/en/latest/getting-started/configuration.html#set-up-remote-control for instructions on setting up the certificates and keys for remote-control via TLS. On the unbound_exporter side you will need to set the `-unbound.ca`, `-unbound.cert`, and `-unbound.key` flags to point to valid files that will trust the Unbound server's certificate and be trusted by Unbound in return.
# Extended statistics
From the Unbound [statistics doc](https://www.nlnetlabs.nl/documentation/unbound/howto-statistics/): Unbound has an option to enable extended statistics collection. If enabled, more statistics are collected, for example what types of queries are sent to the resolver. Otherwise, only the total number of queries is collected. Add the following to your `unbound.conf`.
server:
extended-statistics: yes