[Product Data] First step in gateway usage data collection #4963
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR is the first step towards collecting data on gateway usage. It builds up on @neacsu's old code for what was then nym-connect.
What it does
Exposes unique users count and connection time histogram on the$d$ exposes data from day $d-1$ .
metrics/sessionsendpoint of the self-described API on entry-gateways. For the time being, data is collected by probing theActiveClientStoreevery minute and extracting data from this. Data is stored internally and exposed on the next day, i.e. UTC dayFuture plans
The
statisticsmodule will evolve as we add collection for product data and censorship resistance study. The collection will also eventually switch from probing to event-based for more accurate data.This change is