Gather PowerDNS Recursor stats with Telegraf #108
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to get PowerDNS Recursor Stats into InfluxDB and thus Grafana, using the Telegraf input plugin.
We don't really have any insight on the recursors' health and state yet, only indirectly from dnsdist in front of them.
This basically follows the guide from the plugin README.
The only difference is that we don't create a separate directory under
/runfor the listening sockets (socket_dir), but reuse/run/pdns-recursorwhich systemd already creates for the recursor. Creating new directories in/runis ugly, because it is a virtual file system and everything's lost after reboot.This also means we have to set the mode for
/run/pdns-recursorto0775so thepdnsgroup has write access as well (not only the user). Thankfully all-mighty systemd gives us the optionRuntimeDirectoryModefor this.I have no idea whether this works like this. A few fixes might be required after a test rollout.
(I am opening the PR now because I have it ready, but won't deploy this until tomorrow. So please don't merge, unless you want to deploy yourself.)