On Tuesday, October 5, 2021 11:13:27 PM CEST Bleedangel Tor Admin wrote: > i think the troubleshooting guide should contain directions to enable > metricsport, and how to view the results: +1 > ... > > To enable metricsport for advanced diagnosis: > > In torrc set MetricsPort and MetricsPortPolicy flags as follows: > > MetricsPort <server ip address>:<port> > MetricsPortPolicy accept <ip address to accept metricsport queries from> > > it is good policy to only allow connections to the metricsport port from > localhost as follows: > > MetricsPort 127.0.0.1:9035 #This will open the metricsport > server on port 9035, listening on localhost (127.0.0.1). MetricsPortPolicy > accept 127.0.0.1 #This will allow only localhost (127.0.0.0) to query > the metricsport server. > > Once these are set and the configuration reloaded (via SIGHUP or tor > restart), the data can be queried as follows: > > wget http://127.0.0.1:9035/metrics -O metricsport.txt > > This will place a file in the current directory called 'metricsport.txt' > that can be used to troubleshoot the overloaded relay issues via the > information in this document > > ... Great summary -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays