Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion for usage data collection #1482

Merged
merged 1 commit into from
Nov 3, 2024
Merged

Suggestion for usage data collection #1482

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/roadmap/usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,7 @@ Finally, we would need a number of **timestamps**:
The user could inspect the usage data with **netlab usage show**, reset it with **netlab usage reset**, and upload it with **netlab usage upload**.

While it's relatively easy to implement the data collection part, the infrastructure supporting the uploads remains a mystery.

## Option A - separate GitHub project ```netlab_usage```
One option is to use GitHub for collecting usage data: Using a separate repo, Netlab would push and commit the usage file to a location under that repo.
Security wise, this would require an access token with limited write permissions (hence the separate repo - not sure if we could restrict access well enough within 1 repo)