1PMDABIND2(1)                General Commands Manual               PMDABIND2(1)
2
3
4

NAME

6       pmdabind2 - BIND performance metrics domain agent (PMDA)
7

DESCRIPTION

9       This  PMDA  extracts performance data from BIND (Berkeley Internet Name
10       Domain).  It enables collection of most of the statistics metrics  from
11       the Bind server version 9 or later, which includes:
12
13       · overall memory statistics
14
15       · overall   per-query   statistics   (general  queries,  EDNS/truncated
16         responses, Update/Notify/AXFR/IXFR messages)
17
18       · overall error statistics  (Rejected,  SERVFAIL,  Update/XFR  failures
19         ...)
20
21       · overall statistics per transport protocol, EDNS and per version of IP
22         protocol
23
24       · resolver statistics (successes, errors, round-trip times  in  several
25         ranges)
26
27       · detailed  per-socket statistics with respect to the transport protcol
28         and IP version including errors
29
30       · detailed per-file-descriptor statistics including errors
31
32       The PMDA performs per-second collection of the whole data set (148 met‐
33       rics on the test environment) with modest requirements (2% CPU usage on
34       Intel i7-4700MQ @2.4 GHz, cca 30 MB RAM).
35
36       If more than 1 requests/sec is performed, the memoized values are  used
37       so  that the statistics interface of the Bind server does not get over‐
38       loaded.
39

INSTALLATION

41       Configure BIND to export XML statistics via its REST  interface.   This
42       requires  BIND configuration to enable statistics exporting locally (at
43       least).
44
45           statistics-channels {
46               inet 127.0.0.1 port 8080 allow { 127.0.0.1; };
47           }
48           options { zone-statistics yes; }
49
50       The hostname (localhost), port (8080  above)  and  other  configuration
51       information  must  be  specified in both the BIND configuration file as
52       well as the $PCP_PMDAS_DIR/bind2/bind2.conf file.
53
54             # cd $PCP_PMDAS_DIR/bind2
55             # [ edit bind2.conf ]
56               host=localhost.localdomain:8080
57
58       Once this is setup, you can access the names and values for  the  bind2
59       performance metrics by doing the following as root:
60
61             # cd $PCP_PMDAS_DIR/bind2
62             # ./Install
63
64       To uninstall, do the following as root:
65
66             # cd $PCP_PMDAS_DIR/bind2
67             # ./Remove
68
69       pmdabind2 is launched by pmcd(1) and should never be executed directly.
70       The Install and  Remove  scripts  notify  pmcd(1)  when  the  agent  is
71       installed or removed.
72

FILES

74       $PCP_PMDAS_DIR/bind2/bind2.conf
75           mandatory configuration file listing monitored bind2 instances
76
77       $PCP_PMDAS_DIR/bind2/Install
78           installation script for the pmdabind2 agent
79
80       $PCP_PMDAS_DIR/bind2/Remove
81           undo installation script for the pmdabind2 agent
82
83       $PCP_LOG_DIR/pmcd/bind2.log
84           default log file for error messages from pmdabind2
85

PCP ENVIRONMENT

87       Environment variables with the prefix PCP_ are used to parameterize the
88       file and directory names used by PCP. On each  installation,  the  file
89       /etc/pcp.conf  contains  the  local  values  for  these variables.  The
90       $PCP_CONF variable may be used to specify an alternative  configuration
91       file, as described in pcp.conf(5).
92

SEE ALSO

94       pmcd(1), pmdanamed(1), named.conf(5) and named(8).
95
96
97
98Performance Co-Pilot                  PCP                         PMDABIND2(1)
Impressum