[Improvement]: Remove unnecessary policy engine call in traffic logging
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
Gateway
Please select the aspect the issue is related to
Aspect/Logging (Log formats, instrumentation, improvements)
Suggested Improvement
Currently all system policies process request response headers and bodies. https://github.com/wso2/api-platform/blob/6fa941ae3c77e1a69cc498a1079881f338137f67/gateway/system-policies/analytics/analytics.go#L154
Configuring this based on [collector] configs would resolve this issue
Related Issues
No response
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 with gateway/system-policies/analytics/analytics.go at the referenced line and inspect how collector configuration is represented and consumed. Determine the configuration and policy-flow changes needed so request and response headers and bodies are processed only when enabled by collector settings, then verify the affected logging behavior with the relevant gateway tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100