[prev in list] [next in list] [prev in thread] [next in thread]
List: tor-dev
Subject: Re: [tor-dev] onionoo.tpo stuck at 2018-01-21 22:00
From: Karsten Loesing <karsten () torproject ! org>
Date: 2018-01-26 10:54:07
Message-ID: 063e73b7-9b4a-ff28-3ad4-b18f2c1ffef4 () torproject ! org
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
[Attachment #4 (multipart/mixed)]
On 2018-01-26 11:34, nusenu wrote:
> > What we can do, though, is think about providing more history in
> > Onionoo, so that you can give up on archiving Onionoo data.
>
> It is nice of you to consider that but it is not necessary (at least for me)
> I can life with my current hacks and other probably don't need more history,
> and you have already enough stuff on your plate.
Okay.
> > > Do you monitor onionoo for such problems ("relays_published" timestamp \
> > > remaining unchanged for >1-2 hours)? Would you find something like that \
> > > useful?
> >
> > We do have such monitoring, yes.
>
> So my email was redundant to your nagios check?
>
> Would it be possible to publish these alerts on a mailing list? :)
Not a crazy idea! I opened a ticket for further discussing this:
https://trac.torproject.org/projects/tor/ticket/25035
All the best,
Karsten
["signature.asc" (application/pgp-signature)]
[Attachment #8 (text/plain)]
_______________________________________________
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic