Gateway should not publish analytics for non matched routes
Open
Nobody has claimed this yet.
Type/Task
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
We have to consider whether we should publish analytics or not for 404 scenarios. May match context or may not match.
Contributor guide
No contributing guide indexed for this repository
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 tracing the gateway's handling of 404 and non-matched routes, then locate where analytics are published. Clarify whether analytics should be emitted when route matching fails, including the cases shown in the description. Done means the behavior is decided, implemented, and covered by tests for matched and non-matched routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100