#24831 closed enhancement (wontfix)

Consider providing more/less fine grained data for Realy Search graphs

Reported by: irl Owned by: irl
Priority: Medium Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords:
Cc: karsten Actual Points:
Parent ID: #24155 Points:
Reviewer: Sponsor:

Description

In relay search, if a graph is not available it shows a "No Data Available" image. As the data is present anyway, perhaps these graphs can be shown with only the last X data points from a later graph with the interval then increased to be that of the later graph.

Child Tickets

Change History (6)

comment:1 Changed 17 months ago by iwakeh

Summary: Consider providing more/less fine grained graphs where currently they are notConsider providing more/less fine grained data for Realy Search graphs

Adapted title to reflect that Onionoo provides data not graphs; the graph related part belongs to Relay Search (ticket?).
This feature would mean bigger Onionooo docs and more calculation on Onionoo's side; see also meeting minutes from 2018-01-08.14:39 onward for some more background and also #24155.

comment:2 Changed 17 months ago by karsten

There are two reasons why Onionoo would not provide data for a given graph (let's take 3 months as example):

  1. Data is not available on the granularity that is typically plotted for the desired time frame, but only on a higher granularity. This is currently biting us with relays switching from 4 to 24 hours granularity for bandwidth data. Onionoo does not include this data, because it would be exactly the same as the graph data for longer time periods. Clients can check whether there is graph data available for the next longer periods. In the example, check whether there's a 1 year or 5 years data object and just plot the last 3 months.
  2. Data is available on the right granularity, but only for part of the graph interval that is already contained in a graph with shorter time period. In the example, if a relay or bridge is around for less than 1 month, it wouldn't have a 3 months data set, but clients could fall back to using the 1 month or 1 week or 3 days data set. Note that Onionoo makes sure that at least one graph is available in such a case.

Would it be difficult to put an ordered list of graph intervals into the client code, and whenever the requested graph cannot be found, first search towards longer graph periods and then towards shorter graph periods? Adding all this redundant data feels like a kludge. We could even document the approach taken by Relay Search in the Onionoo protocol specification as recommendation for other clients, if that would help.

comment:3 Changed 17 months ago by irl

Component: Metrics/OnionooMetrics/Relay Search
Owner: changed from metrics-team to irl
Status: newaccepted

Ok, I'll try to fix this in Relay Search first. This is probably the "right way" to do it.

comment:4 Changed 16 months ago by irl

Cc: karsten added

I am inclined to mark this as wontfix for now, waiting for a single history object to be implemented in Onionoo.

karsten - What do you think?

comment:5 Changed 16 months ago by karsten

Plausible, yes.

comment:6 Changed 16 months ago by irl

Resolution: wontfix
Status: acceptedclosed

Ok, waiting for a single history object in Onionoo before making changes here.

Note: See TracTickets for help on using tickets.