For a tor relay that is not neccessary. After I thought about this in the past I decided it so after local watching. Now I use "htop" and "bwm-ng", "nload" and "nyx" via SSH on the remote server. You can use the website "uptime monitor" if you want to get a mail after server crash or other network errors. My preference is the tor monitoring network https://metrics.torproject.org. Why you want to use a big monitoring solution? If your tor relay is a second paylod on the server this ist ok, but this is not the right discussion channel here.

Olaf

Am 08.12.18 um 10:01 schrieb petrarca@protonmail.ch:

I was thinking about setting up a monitoring of a Tor-Relay using Telegraf, InfluxDB and Grafana. Although I did read quite some documenation about it already I thought it might be good to check for possible experiences made here before spending (wasting) too much time trying it out myself.

Questions I could not answer yet myself include e.g.

• What will be the performance impact of running Telegraf on a Tor-Realy (CPU, disk, I/O,...)?
• What happens if the InfluxDB (running on another system) is not reachable (maintenance, outages) - is the data lost or buffered somehow?
• I would like to also keep see old/historical data but not as granular as more recent data - is there any way to boild down old data, e.g. to only keep hourly data for data older that a month etc.?

There are an overwhelmingly number of monitoring possibilities (munin, collecd, monit, nyx, RRDtool, Cacti, Monitorix, Nagios, Zabbix,...) out there and one could easily spend days if not weeks with reading and testing. So any kind of shared experiences, hints or tips are more than welcome.

.

---

tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays