[API Gateway] Access logs
Open
theme/api-gw
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
#### Feature Description
Currently Consul 1.15.0 and above have the ability to turn on access logs for all gateways with the exception of Consul API Gateway. This issue is to track the support for access logs for proxies that are managed and deployed by Consul API Gateway.
#### Use Case(s)
VMs and K8s API Gateway deployments.
Contributor guide
Research direction
The issue names no files or tests. Start by locating Consul API Gateway’s proxy deployment path and the existing access-log support for other gateways, then compare VM and Kubernetes deployments. Done means access logs work for proxies managed and deployed by the API Gateway in both stated environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, devops, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100