powerdns

README

PowerDNS Authoritative Server monitoring with Netdata

PowerDNS Authoritative Server is a versatile nameserver which supports a large number of backends.

This module monitors one or more PowerDNS Authoritative Server instances, depending on your configuration.

It collects metrics from the internal webserver.

Used endpoints:

• /api/v1/servers/localhost/statistics

Requirements

For collecting metrics via HTTP, we need:

• enabled webserver.
• enabled HTTP API.

Metrics

All metrics have "powerdns." prefix.

Metric	Scope	Dimensions	Units
questions_in	global	udp, tcp	questions/s
questions_out	global	udp, tcp	questions/s
cache_usage	global	query-cache-hit, query-cache-miss, packetcache-hit, packetcache-miss	events/s
cache_size	global	query-cache, packet-cache, key-cache, meta-cache	entries
latency	global	latency	microseconds

Configuration

Edit the go.d/powerdns.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/powerdns.conf

To add a new endpoint to collect metrics from, or change the URL that Netdata looks for, add or configure the name and url values. Endpoints can be both local or remote as long as they expose their metrics on the provided URL.

Here is an example with two endpoints:

jobs:
  - name: local
    url: http://127.0.0.1:8081
    headers:
      X-API-KEY: secret  # static pre-shared authentication key for access to the REST API (api-key).

  - name: remote
    url: http://203.0.113.0:8081
    headers:
      X-API-KEY: secret  # static pre-shared authentication key for access to the REST API (api-key).

For all available options, see the PowerDNS Authoritative Server collector's configuration file.

Troubleshooting

To troubleshoot issues with the powerdns collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

• Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

  cd /usr/libexec/netdata/plugins.d/
  

• Switch to the netdata user.

  sudo -u netdata -s
  

• Run the go.d.plugin to debug the collector:

  ./go.d.plugin -d -m powerdns
  

Documentation

Index

• type AuthoritativeNS
  • func New() *AuthoritativeNS
  • func (ns *AuthoritativeNS) Charts() *module.Charts
  • func (ns *AuthoritativeNS) Check() bool
  • func (ns *AuthoritativeNS) Cleanup()
  • func (ns *AuthoritativeNS) Collect() map[string]int64
  • func (ns *AuthoritativeNS) Init() bool
• type Config

Types

type AuthoritativeNS

type AuthoritativeNS struct {
	module.Base
	Config `yaml:",inline"`
	// contains filtered or unexported fields
}

func New

func New() *AuthoritativeNS

func (*AuthoritativeNS) Charts

func (ns *AuthoritativeNS) Charts() *module.Charts

func (*AuthoritativeNS) Check

func (ns *AuthoritativeNS) Check() bool

func (*AuthoritativeNS) Cleanup

func (ns *AuthoritativeNS) Cleanup()

func (*AuthoritativeNS) Collect

func (ns *AuthoritativeNS) Collect() map[string]int64

func (*AuthoritativeNS) Init

func (ns *AuthoritativeNS) Init() bool

type Config

type Config struct {
	web.HTTP `yaml:",inline"`
}