Documentation

PowerDNS Input Plugin

This plugin gathers metrics from PowerDNS servers using unix sockets.

This plugin will need access to the powerdns control socket.

Introduced in: Telegraf v0.10.2 Tags: server OS support: all

Global configuration options

In addition to the plugin-specific configuration settings, plugins support additional global and plugin configuration settings. These settings are used to modify metrics, tags, and field or create aliases and configure ordering, etc. See the CONFIGURATION.md for more details.

Configuration

# Read metrics from one or many PowerDNS servers
[[inputs.powerdns]]
  # An array of sockets to gather stats about.
  # Specify a path to unix socket.
  #
  # If no servers are specified, then '/var/run/pdns.controlsocket' is used as the path.
  unix_sockets = ["/var/run/pdns.controlsocket"]

Permissions

Telegraf will need access to the powerdns control socket. On many systems this can be accomplished by adding the telegraf user to the pdns group:

usermod telegraf -a -G pdns

Additionally, telegraf may need additional permissions. Look at the socket-mode PowerDNS option to set permissions on the socket.

Metrics

  • powerdns
    • corrupt-packets
    • deferred-cache-inserts
    • deferred-cache-lookup
    • dnsupdate-answers
    • dnsupdate-changes
    • dnsupdate-queries
    • dnsupdate-refused
    • packetcache-hit
    • packetcache-miss
    • packetcache-size
    • query-cache-hit
    • query-cache-miss
    • rd-queries
    • recursing-answers
    • recursing-questions
    • recursion-unanswered
    • security-status
    • servfail-packets
    • signatures
    • tcp-answers
    • tcp-queries
    • timedout-packets
    • udp-answers
    • udp-answers-bytes
    • udp-do-queries
    • udp-queries
    • udp4-answers
    • udp4-queries
    • udp6-answers
    • udp6-queries
    • key-cache-size
    • latency
    • meta-cache-size
    • qsize-q
    • signature-cache-size
    • sys-msec
    • uptime
    • user-msec

Tags

  • tags: server=socket

Example Output

powerdns,server=/var/run/pdns.controlsocket corrupt-packets=0i,deferred-cache-inserts=0i,deferred-cache-lookup=0i,dnsupdate-answers=0i,dnsupdate-changes=0i,dnsupdate-queries=0i,dnsupdate-refused=0i,key-cache-size=0i,latency=26i,meta-cache-size=0i,packetcache-hit=0i,packetcache-miss=1i,packetcache-size=0i,qsize-q=0i,query-cache-hit=0i,query-cache-miss=6i,rd-queries=1i,recursing-answers=0i,recursing-questions=0i,recursion-unanswered=0i,security-status=3i,servfail-packets=0i,signature-cache-size=0i,signatures=0i,sys-msec=4349i,tcp-answers=0i,tcp-queries=0i,timedout-packets=0i,udp-answers=1i,udp-answers-bytes=50i,udp-do-queries=0i,udp-queries=0i,udp4-answers=1i,udp4-queries=1i,udp6-answers=0i,udp6-queries=0i,uptime=166738i,user-msec=3036i 1454078624932715706

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2