agrc / agrc/serverless-print-proxy
Analytics
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We need to come up with some sort of analytics for this application. Right now, I'm just logging the account number for each request. Perhaps that would be enough with some sort of report through Log Analytics in GCP?
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
Start by reviewing how the application currently logs the account number for each request. Then evaluate whether GCP Log Analytics and a report would meet the application's analytics needs. Done means the analytics approach, required data, and reporting outcome are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, typescript
- Domain
- analytics, backend-api-design, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100