Opened 6 weeks ago

Last modified 6 weeks ago

#31345 new enhancement

Add "last_changed_address_or_port" as timestamp metric to relay search detail page?

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

Description

Can the "last_changed_address_or_port" timestamp value reported by onionoo (https://onionoo.torproject.org/details) for an individual relay be added as a text field metric to the individual relay search details page? Ex: https://metrics.torproject.org/rs.html#details/A4A25EDAB880FF4200F4C21316F3B9E072C9F466
The value is helpful when making changes to addresses and ports and knowing when they're recognized by the network - this can happen multiple times when moving a relay between servers, IP addresses, and ports to get the best configuration and performance.

If this is acceptable and it's helpful - I can take a pass at submitting a pull request?
Could a link be shared to where JSON from onionoo is parsed into the web page relay search results for metrics.torproject.org and I can take a pass at submitting the code?

Child Tickets

Change History (2)

comment:1 Changed 6 weeks ago by jk

New to all of this effort so putting some thoughts here on the how to accomplish:

Rough workflow? Seems we'd want to parse data into the database for storage, than connect up to displaying from the database onto the web page?

For code source (might be out-dated?): https://github.com/torproject/metrics-web ?
Seems web page itself: https://github.com/torproject/metrics-web/blob/master/src/main/resources/web/templates/rs/details/router.html

comment:2 Changed 6 weeks ago by karsten

Cc: metrics-team added
Component: Metrics/WebsiteMetrics/Relay Search

Thanks for the suggestion! Moving to the right component and leaving the questions for irl.

Note: See TracTickets for help on using tickets.