Opened 9 months ago

Last modified 3 months ago

#23509 assigned enhancement

Implement family-level pages showing aggregated graphs

Reported by: cypherpunks Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords: metrics-2018
Cc: torproject.org@… Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:

Description

Currently atlas is about single relays, many operators run more than a single relay and would like to see the aggregated data of all their relays on a single page with the graphs showing all relays in stacked way.
This allows them to see how they are doing across all their relays.

example graphs:
https://nos-oignons.net/Services/index.en.html

To avoid discussing how to identify MyFamilies lets just use onionoo lookup:
https://atlas.torproject.org/#search/family:<fingerprint of an arbitrary relay>

This would also create an incentive for properly configuring MyFamily since incorrect set MyFamily would result

relay operators find this useful (counted ~11)
https://lists.torproject.org/pipermail/tor-relays/2017-September/012942.html
https://twitter.com/nusenu_/status/907366138149044224

Child Tickets

Change History (10)

comment:1 Changed 9 months ago by Ralph

Cc: torproject.org@… added

comment:2 Changed 9 months ago by arma

If it's convenient, it would be smart to build it in a way that we can do other aggregations later. I'm thinking "country" and "AS" as my examples, but maybe there will be other examples too.

Though heck, if we're thinking of it as an onionoo lookup, I wonder if there are already onionoo lookups for country and AS, and then we're done?

comment:3 in reply to:  2 Changed 9 months ago by cypherpunks

Replying to arma:

Though heck, if we're thinking of it as an onionoo lookup, I wonder if there are already onionoo lookups for country and AS, and then we're done?

yes there are, example for AS:
https://atlas.torproject.org/#search/as:AS396507
example for country:
https://atlas.torproject.org/#search/country:tr

comment:4 Changed 9 months ago by karsten

Please also find #23517 for a related idea.

comment:5 Changed 9 months ago by karsten

Summary: implement family-level pages showing aggregated graphsImplement family-level pages showing aggregated graphs

Capitalize summary.

comment:6 Changed 9 months ago by karsten

Keywords: metrics-2018 added

comment:7 Changed 7 months ago by irl

I have a plan for this that involves a new #/aggregate/details/(onionoo lookup) route using an aggregatesCollection with an aType of "all" to give a single row.

There needs to be a switch in aggregatesCollection to allow collecting more fields than normal (while not doing this on the search page) and then an aggregate details template to show the information.

For the graphs it may be possible to stack them as on the nos-oignons.net but I'd rather not be doing a lot of aggregating large documents in the JavaScript. Maybe at a limit it will just refuse to attempt to plot.

comment:8 Changed 5 months ago by irl

Owner: changed from irl to metrics-team
Status: newassigned

Removing these tickets from my queue due to time constraints, and to let others have a go if they wish.

Guidelines for contributing to Relay Search can be found at: https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam/RelaySearch

comment:9 Changed 4 months ago by irl

Points: 3

comment:10 Changed 3 months ago by iwakeh

Please be aware of the start for RS into Metrics-Web integration and also refer to the branch in this comment of the parent ticket.

Note: See TracTickets for help on using tickets.