Opened 7 years ago

Closed 7 years ago

#7652 closed enhancement (implemented)

Can we remove relay flags graph on hourly detail?

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

All metrics graphs except the relay flags graph have a detail level of 1 day. The relay flags graph further provides 1 hour detail.

I'm planning to remove the option to display the relay flags graph on hourly detail. The reason is that I want to remove data on this level of detail from the database, making metrics-web scale better, making it easier to add new graphs in the future. This graph is blocking me there.

How sad will people be if the graph on hourly detail goes away? Are there important reasons to keep it? If not, I'll disable that option in a week from now.

Child Tickets

Change History (3)

comment:1 Changed 7 years ago by bastik

(I intended to ask per mail, but this ticket is better suited, I assume)

I assumed that the hourly detail on the flags existed to see/check if there were any glitches in the consensus.

Authorities get together once an hour; if there's something wrong and half the stable relays lose their stable flag for an hour the hourly graph would show that, while the daily does not. At least not that clear. (Is there another way to see something like that happening?) For me it was THE reason it would exist. Sudden changes, where one would look into the consensus of this hour. (Were there other reasons it existed?)

(For example if the graph shows 20 more relays with the running flag than in the previous hour it wouldn't be a good indicator to say 20 relays joined in that hour, because it could be 30, as 10 left.)

I get the scaling part, but what prevent adding new graphs (if hourly is kept for the flags)?

Questions in brackets can be answered if there's enough time to do so.

comment:2 in reply to:  1 Changed 7 years ago by karsten

Replying to bastik:

I assumed that the hourly detail on the flags existed to see/check if there were any glitches in the consensus.

Authorities get together once an hour; if there's something wrong and half the stable relays lose their stable flag for an hour the hourly graph would show that, while the daily does not. At least not that clear. (Is there another way to see something like that happening?) For me it was THE reason it would exist. Sudden changes, where one would look into the consensus of this hour. (Were there other reasons it existed?)

Yes, you would see sudden changes to a single relay flag, like Stable, but also sudden changes to the absolute number of relays.

(For example if the graph shows 20 more relays with the running flag than in the previous hour it wouldn't be a good indicator to say 20 relays joined in that hour, because it could be 30, as 10 left.)

True, but if a large number of relays joins the network, it's very likely that you'd see it. Or rather, it's highly unlikely that an almost equal number of relays would leave the network in the same hour.

So, to answer your question how you'd detect glitches in the consensus, here are three services or service ideas doing that:

  • The consensus-health service tells you whether there are problems with the consensus process.
  • atagar's consensus-tracker service looks out for new relays adding unusual amounts of bandwidth to the network at once.
  • atagar and Runa were planning to extend the consensus-tracker service to do advanced checks for unusual things happening in the Tor network. There's no code for this service yet, and I don't think anybody's working on it right now.

I get the scaling part, but what prevent adding new graphs (if hourly is kept for the flags)?

It would be possible to add new graphs on hourly detail, but that contradicts the original goal of this ticket, which is to make the metrics database scale better.

Thanks for your feedback!

comment:3 Changed 7 years ago by karsten

Resolution: implemented
Status: newclosed

Disabled relay flags graph on hourly detail. Closing.

Note: See TracTickets for help on using tickets.