Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-16 Thread Damian Johnson
> It might be smartest to just put in an exception for moria1's > HSDir votes, since we know it's being different. Suppressed any notices for HSDir flags. Also fixed the time based suppression for the check (it should have sent one notice a day rather than one an hour).

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-16 Thread nusenu
Roger Dingledine: > It might be smartest to just put in an exception for moria1's > HSDir votes, since we know it's being different. yes, please :) and it would also be nice to have: https://trac.torproject.org/projects/tor/ticket/25222 so we can filter for those emails that we care about

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-15 Thread Roger Dingledine
On Mon, Feb 12, 2018 at 08:31:13AM -0800, Damian Johnson wrote: > Nope, it is deployed (if by 'deployed' you mean DocTor is presently > performing this check). From David's reply about moria1 it sounds like > any check of this sort may be a red herring since they experiment with > moria1, but I'll

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-12 Thread nusenu
Damian Johnson: >> thanks for implementing the new check so fast. > > No problem! Thanks for suggesting it. > >> This is also very useful but slightly different from what I had in mind, >> because it would not trigger if dirauths upgrade from A to B in the >> same hour and most exits, guards or

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-12 Thread David Goulet
On 11 Feb (21:21:00), nusenu wrote: > > Thanks nusenu! Nice idea, added it to DocTor... > > thanks for implementing the new check so fast. > > > https://gitweb.torproject.org/doctor.git/commit/?id=8945013 > > > > It gives a notice if flags issued by an authority are 50% different > > from the

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-11 Thread Damian Johnson
> thanks for implementing the new check so fast. No problem! Thanks for suggesting it. > This is also very useful but slightly different from what I had in mind, > because it would not trigger if dirauths upgrade from A to B in the > same hour and most exits, guards or hsdirs are gone due to a

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-11 Thread Tom Ritter
I think the doctor notification is the best mechanism. I'm not opposed to adding more graphs to consensus-health, but I think I'd want to coordinate with the metrics team. There was talk about them absorbing consensus health in some capacity, so I'd prefer to avoid doing a lot of work on graphs

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-11 Thread nusenu
> Thanks nusenu! Nice idea, added it to DocTor... thanks for implementing the new check so fast. > https://gitweb.torproject.org/doctor.git/commit/?id=8945013 > > It gives a notice if flags issued by an authority are 50% different > from the conensus. Presently there's only one instance of

Re: [tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-11 Thread Damian Johnson
Thanks nusenu! Nice idea, added it to DocTor... https://gitweb.torproject.org/doctor.git/commit/?id=8945013 It gives a notice if flags issued by an authority are 50% different from the conensus. Presently there's only one instance of that... [consensus-health] NOTICE: moria1 had 756 HSDir flags

[tor-dev] monitoring significant drops of flags in dirauth votes

2018-02-11 Thread nusenu
Hi Damian and Tom, Roger discovered that dannenberg did not include any exit flags in certain votes anymore [1]. It would be great if we would detect and notify about such events in the future. I see two places where this could be added: DocTor: a new check that alerts on events where a