Opened 6 months ago

Last modified 6 months ago

#32690 needs_information enhancement

Create new directive HiddenServiceExportStats.

Reported by: moonsikpark Owned by: moonsikpark
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs
Cc: teor, dgoulet, ahf Actual Points:
Parent ID: #32511 Points:
Reviewer: Sponsor:


Currently HiddenServiceExportCircuitID specifies the protocol. As we move towards exporting as much stats as we can, I think it's better to create a new directive(HiddenServiceExportStats) for the protocol only.

Also, I need some opinions on the directives.

  1. Create directive per stat(HiddenServiceExport*), make all of them bound to the hidden service (in hs_service_config_t).
  2. Create directive per stat, only HiddenServiceExportStats bounds to the hidden service and others are global (in or_options_st).
  3. Don't create directive per stat, Only one directrive HiddenServiceExportStats, bound to the hidden service, exports all.

Child Tickets

Change History (3)

comment:1 Changed 6 months ago by moonsikpark

Type: defectenhancement

comment:2 Changed 6 months ago by teor

Status: assignedneeds_information

Here's some context for this question:

How do you expect people to use this feature? It's hard for me to decide between these options, when I don't know how they will be used.

Unless there is some compelling use case for per-service or per-field options, I'd prefer this design:

  1. Only one directive HiddenServiceExportStats, global, exports all fields, for all hidden services.

I also don't think it's helpful to call this data "Stats", because Tor already has a statistics system, on relays, that works via extra-info descriptors.

Let's say "HiddenServiceExportCircuitInfo" or something similar.

Last edited 6 months ago by teor (previous) (diff)

comment:3 Changed 6 months ago by dgoulet

Milestone: Tor: unspecified
Note: See TracTickets for help on using tickets.