Opened 8 years ago

Closed 2 years ago

#6675 closed enhancement (wontfix)

Support grouping by contact

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


I'd suggest to add a feature to group relays by contact.
Only non-empty contacts should be grouped together.

It will likely result in similar groups as defined in #6662.

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by tyseom

Cc: nusenu@… added

comment:3 Changed 3 years ago by karsten

Severity: Normal
Summary: group by contactSupport grouping by contact

Tweak summary a bit.

comment:4 Changed 2 years ago by karsten

Owner: set to metrics-team
Status: needs_reviewassigned

comment:5 Changed 2 years ago by irl

Component: Metrics/CompassMetrics/Atlas

In #23517 it is planned to merge Compass functionality with Relay Search (formerly known as Atlas). These tickets may be relevant to that work and so these are being reassigned to the Metrics/Atlas component.

comment:6 Changed 2 years ago by irl

Relay Search supports the following queries:

Aggregate simple data in single table row:

Show all relays matching in multiple table rows:

A details view with aggregated graphs may be added in #23509.

nusenu: Does this solve your use case or do you think grouping by contact is still useful? This is easier than grouping by family but it would only group by exact matches and every time we add a grouping the code becomes exponentially more complex in the way it's currently implemented.

comment:7 Changed 2 years ago by irl

Resolution: wontfix
Status: assignedclosed

In the future we may support aggregation based on any Onionoo field, but implementing contact aggregation alone is not something that is likely to happen. Having implemented #6855 the code has reached the maximum level of complexity that I feel is going to be maintainable.

Note: See TracTickets for help on using tickets.