Sophie

Sophie

distrib > Mandriva > 2010.1 > i586 > media > contrib-updates > by-pkgid > 563affe035311228f138962d4d47d4fd > files > 45

pdns-3.0.1-0.1mdv2010.2.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Index of all Authoritative Server metrics</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="PowerDNS manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Index of all Authoritative Server settings"
HREF="all-settings.html"><LINK
REL="NEXT"
TITLE="Supported record types and their storage"
HREF="types.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>PowerDNS manual</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="all-settings.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="types.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="METRICS"
></A
>Chapter 16. Index of all Authoritative Server metrics</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="COUNTERS-VARIABLES"
>16.1. Counters &amp; variables</A
></H1
><P
>      A number of counters and variables are set during PDNS Authoritative Server operation. These can be queried with the init.d
      <B
CLASS="COMMAND"
>dump</B
>, <B
CLASS="COMMAND"
>show</B
> and <B
CLASS="COMMAND"
>mrtg</B
> commands, or viewed with the
      webserver.
      </P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="COUNTERS"
>16.1.1. Counters</A
></H2
><P
>      <P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>corrupt-packets</DT
><DD
><P
>Number of corrupt packets received</P
></DD
><DT
>latency</DT
><DD
><P
>Average number of microseconds a packet spends within PDNS</P
></DD
><DT
>packetcache-hit</DT
><DD
><P
>Number of packets which were answered out of the cache</P
></DD
><DT
>packetcache-miss</DT
><DD
><P
>Number of times a packet could not be answered out of the cache</P
></DD
><DT
>packetcache-size</DT
><DD
><P
>Amount of packets in the packetcache</P
></DD
><DT
>qsize-a</DT
><DD
><P
>Size of the queue before the transmitting socket.</P
></DD
><DT
>qsize-q</DT
><DD
><P
>Number of packets waiting for database attention</P
></DD
><DT
>servfail-packets</DT
><DD
><P
>Amount of packets that could not be answered due to database problems</P
></DD
><DT
>tcp-answers</DT
><DD
><P
>Number of answers sent out over TCP</P
></DD
><DT
>tcp-questions</DT
><DD
><P
>Number of questions received over TCP</P
></DD
><DT
>timedout-questions</DT
><DD
><P
>Amount of packets that were dropped because they had to wait too long internally</P
></DD
><DT
>udp-answers</DT
><DD
><P
>Number of answers sent out over UDP</P
></DD
><DT
>udp-questions</DT
><DD
><P
>Number of questions received over UDP</P
></DD
></DL
></DIV
>
    </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN4091"
>16.1.2. Ring buffers</A
></H2
><P
>	  Besides counters, PDNS also maintains the ringbuffers. A ringbuffer records events, each new event gets a place
	  in the buffer until it is full. When full, earlier entries get overwritten, hence the name 'ring'.
	</P
><P
>      By counting the entries in the buffer, statistics can be generated. These statistics can currently only be viewed 
      using the webserver and are in fact not even collected without the webserver running. 
    </P
><P
>      The following ringbuffers are available:
    </P
><P
>    <P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>Log messages (logmessages)</DT
><DD
><P
>All messages logged</P
></DD
><DT
>Queries for existing records but for a type we don't have (noerror-queries)</DT
><DD
><P
>Queries for, say, the AAAA record of a domain, when only an A is available. 
	  Queries are listed in the following format: name/type. So an AAA query for pdns.powerdns.com looks like
	  pdns.powerdns.com/AAAA.</P
></DD
><DT
>Queries for non-existing records within existing domains(nxdomain-queries)</DT
><DD
><P
>If PDNS knows it is authoritative over a domain, and it sees a question for a record in that domain
	    that does not exist, it is able to send out an authoritative 'no such domain' message. Indicates that hosts are
	    trying to connect to services really not in your zone.</P
></DD
><DT
>UDP queries received (udp-queries)</DT
><DD
><P
>	    All UDP queries seen.
	  </P
></DD
><DT
>Remote server IP addresses (remotes)</DT
><DD
><P
>	    Hosts querying PDNS. Be aware that UDP is anonymous - person A can send queries that appear to be coming from
	    person B.
	  </P
></DD
><DT
>Remotes sending corrupt packets (remote-corrupts)</DT
><DD
><P
>	    Hosts sending PDNS broken packets, possibly meant to disrupt service. Be aware that UDP is 
	    anonymous - person A can send queries that appear to be coming from person B.
	  </P
></DD
><DT
>Remotes querying domains for which we are not auth (remote-unauth)</DT
><DD
><P
>	    It may happen that there are misconfigured hosts on the internet which are configured to
	    think that a PDNS installation is in fact a resolving nameserver. These hosts will not
	    get useful answers from PDNS. This buffer lists hosts sending queries for domains which 
	    PDNS does not know about.
	  </P
></DD
><DT
>Queries that could not be answered due to backend errors (servfail-queries)</DT
><DD
><P
>	    For one reason or another, a backend may be unable to extract answers for a certain domain from
	    its storage. This may be due to a corrupt database or to inconsistent data. When this happens,
	    PDNS sends out a 'servfail' packet indicating that it was unable to answer the question. This buffer
	    shows which queries have been causing servfails.
	  </P
></DD
><DT
>Queries for domains that we are not authoritative for (unauth-queries)</DT
><DD
><P
>	    If a domain is delegated to a PDNS instance, but the backend is not made aware of this fact, questions come
	    in for which no answer is available, nor is the authority. Use this ringbuffer to spot such queries.
	  </P
></DD
></DL
></DIV
>
  </P
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="all-settings.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="types.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Index of all Authoritative Server settings</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Supported record types and their storage</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>