Bind stats and graphing

[Treptow, Craig]

I went down the road of having a webserver running onthe DNS server and =
a script that runs "rndc stats".  The script also parses the =
"named.stats" file, and writes the data to a text file that my Cricket =
server picks up via the webserver.

>-----Original Message-----
>From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
>Behalf Of Martin Timbro
>Sent: Tuesday, November 30, 2004 9:31 AM
>To: bind-users at isc.org
>Subject: Bind stats and graphing
>
>
>Hi all,
>
>   I was asked as a project to come up with a strategy to pick=20
>up BIND /=20
>DNS stats from our DNS servers and produce web-based graphics=20
>on a daily=20
>/ weekly / monthly basis. I rarely post on the list asking for=20
>advice (I=20
>have done a bunch of research on my end) but I'd like to find out if=20
>anyone has an easy / intuitive solution for doing this.
>
>   I have read about mrtg graphing with the help of SNMP but we have=20
>strict firewall rules here that almost negate this option...I have=20
>looked at other ways but just can't pin-point which one is=20
>most relevant=20
>to my project.
>
>Thanks for all advice,
>
>
>


-----Message=20Disclaimer-----

This=20e-mail=20message=20is=20intended=20only=20for=20the=20use=20of=20the=20individual=20or
entity=20to=20which=20it=20is=20addressed,=20and=20may=20contain=20information=20that=20is
privileged,=20confidential=20and=20exempt=20from=20disclosure=20under=20applicable=20law.
If=20you=20are=20not=20the=20intended=20recipient,=20any=20dissemination,=20distribution=20or
copying=20of=20this=20communication=20is=20strictly=20prohibited.=20If=20you=20have
received=20this=20communication=20in=20error,=20please=20notify=20us=20immediately=20by
reply=20email=20to=20Connect at principal.com=20and=20delete=20or=20destroy=20all=20copies=20of
the=20original=20message=20and=20attachments=20thereto.=20Email=20sent=20to=20or=20from=20the
Principal=20Financial=20Group=20or=20any=20of=20its=20member=20companies=20may=20be=20retained
as=20required=20by=20law=20or=20regulation.

Nothing=20in=20this=20message=20is=20intended=20to=20constitute=20an=20Electronic=20signature
for=20purposes=20of=20the=20Uniform=20Electronic=20Transactions=20Act=20(UETA)=20or=20the
Electronic=20Signatures=20in=20Global=20and=20National=20Commerce=20Act=20("E-Sign")
unless=20a=20specific=20statement=20to=20the=20contrary=20is=20included=20in=20this=20message.