EclipseFdn / EclipseFdn/open-vsx.org
OpenVSX Traffic Report per Adopter
- Dominant language
- TypeScript
- Stars
- 394
- Forks
- 145
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
## Goal
Produce a report showing requests per second (RPS) and bandwidth per adopter tool (Cursor, Kiro, Windsurf, VSCodium, Theia, Ona, etc.) on the OpenVSX content CDN. The Foundation needs this data to have informed commercial conversations with adopters about their usage of OpenVSX infrastructure.
## Deliverable
A report (spreadsheet or CSV) for a given time period showing RPS per identified adopter tool, plus an "Other / Unidentified" row for remaining traffic.
## Acceptance Criteria
Adopter identification is based on the user-agent string from CDN request logs.
- The report covers the longest available period from the existing CDN log data (earliest possible date is when log streaming to S3 was activated).
- Going forward, the report can be reproduced for any given period with minimal manual effort.
- Data is accurate enough for commercial conversations (statistical estimates based on sampled data are acceptable if documented).
## Open Questions
- Since when is log data available in S3? What time range do we have?
- Can adopter tools be reliably distinguished by their user-agent strings? This needs validation against real log data.
- Is the existing CDN log data complete (all requests) or sampled?
- Are log files retained or removed after consumption by the OpenVSX application?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.