[tor-relays] Overloaded state indicator on relay-search
dgoulet at torproject.org
Fri Oct 1 12:22:28 UTC 2021
On 01 Oct (03:08:20), Andreas Kempe wrote:
> Hello David!
> On Mon, Sep 27, 2021 at 08:22:08AM -0400, David Goulet wrote:
> > On 24 Sep (12:36:17), lists at for-privacy.net wrote:
> > > On Thursday, September 23, 2021 3:39:08 PM CEST Silvia/Hiro wrote:
> > >
> > > > When a relay is in the overloaded state we show an amber dot next to the
> > > > relay nickname.
> > > Nice thing. This flag has noticed me a few days ago.
> > >
> > > > If you noticed your relay is overloaded, please check the following
> > > > support article to find out how you can recover to a "normal" state:
> > > >
> > > > https://support.torproject.org/relay-operators/relay-bridge-overloaded/
> > >
> > > A question about Enabling Metricsport. Is definitely Prometheus necessary?
> > > Or can the Metrics Port write into a LogFile / TextFile?
> > The output format is Prometheus but you don't need a prometheus server to get
> > it.
> > Once opened, you can simply fetch it like this:
> > wget http://<IP_OF_METRICSPORT>:<METRICS_PORT>/metrics -O /tmp/output.txt
> > or
> > curl http://<IP_OF_METRICSPORT>:<METRICS_PORT>/metrics -o /tmp/output.txt
> I've only ever gotten an empty reply when trying to extract metrics
> and I still do on Tor 4.6.7. I have some vague memory of the metrics
> previously only being for hidden services.
> All the metrics mentioned in the overload guide seem to be missing.
> Having a quick look at the Git repository, it seems that only
> 0.4.71-alpha and latest master contain the necessary changes for these
> Is my assumption correct or am I doing something wrong?
Correct, relay metrics are only available on >= 0.4.7.1-alpha. Hopefully, we
should have an 0.4.7 stable by end of year (or around that time).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: not available
More information about the tor-relays