[Task]: Include Deployment handle, kind in Router access log
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Management (Management API or Management Portal UI), Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
@subject
Suggested Improvement
$subject.
Current access log looks like this
[2026-03-22T07:10:23.311Z] "GET /proxymock5v1/m1/models HTTP/2" 200 - 0 14 308 "-" "curl/8.7.1" "8a45bc94-2d29-409e-813a-8067e3505413" "virajg.requestcatcher.com" "104.248.184.153:443"
And it would be great if we can figure out from which API the request was served. (API-UUID or Name + Kind or something)
This is crucial because now we allow users to reuse the same API-Context in different APIs
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 locating the Go router access-log entry point and tracing how the served API or deployment context is available for each request. Compare the current sample log with the proposed identifying information; done means the access log distinguishes the API that served a request, including its deployment handle and kind or an agreed equivalent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100