Munin
We use Munin to gather statistics from our Tor exits. For the configuration of munin-node on the exits (“clientside munin-node”), see munin_resource_monitoring.
This is the “serverside munin” configuration. The only interesting part might be the aggregate bandwidth graph. We don't update this page every time we add or remove a relay, so don't expect everything to match the current configuration.
TODO We could use some more fancy rules to warn when throughput is way below average, ie. when something is wrong with the relay.
/etc/munin/munin.conf
includedir /etc/munin/munin-conf.d contacts me contact.me.command mail -s "Munin notification ${var:host}" NICEEMAIL contact.me.send warning critical [www.torservers.net] address 127.0.0.1 use_node_name yes [psilotorlu.torservers.net] address 212.117.180.65 use_node_name yes # warning when below 50 mbit/s, critical when below 10 mbit/s if_venet0.up.warning 10000000:50000000 if_venet0.up.critical 0:10000000 # ... similar entries for all the other relays ... [torservers.net;aggregates] update no total_bandwidth.graph_args --base 1000 -l 0 total_bandwidth.graph_category Network total_bandwidth.graph_title Aggregated bandwidth total_bandwidth.upload.label upload total_bandwidth.update no total_bandwidth.total.graph yes total_bandwidth.upload.stack \ axigy1=axigy1.torservers.net:if_eth1.up \ axigy2=axigy2.torservers.net:if_eth1.up \ drtornyc1=drtornyc1.torservers.net:if_eth0.up \ drtornyc2=drtornyc2.torservers.net:if_eth0.up \ drtorsea1=drtorsea1.torservers.net:if_eth0.up \ drtorsea2=drtorsea2.torservers.net:if_eth0.up \ assk=assk.torservers.net:if_venet0.up \ assk2=assk2.torservers.net:if_venet0.up \ nforce1=nforce1.torservers.net:if_eth0.up \ nforce2=nforce2.torservers.net:if_eth0.up \ psilotorlu=psilotorlu.torservers.net:if_venet0.up \ voxility1=voxility1.torservers.net:if_eth0.up total_bandwidth.upload.type COUNTER