source-cooperative / source-cooperative/source.coop
[Proposed Feature] Access Logs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 9
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 42
Description
Description of Feature:
Product administrators should be able to view who is accessing their product through the Source data proxy
One idea: we could write logs on a regular interval as parquet files to a special private meta product within each account (e.g. .{account_id}/logs/{product_id}/date=.../...).
What value is this feature adding to Source Cooperative?
Understanding which types of access are driving costs and which mechanism granted them access.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the Source data proxy and its product-access path, then evaluate how access events could be recorded at regular intervals as parquet files in each account's private meta product; done means administrators can identify who accessed a product and which access mechanism drove the access or cost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100