envoyproxy/gateway

Support for nested json access logs

Open

#5,403 opened on Mar 4, 2025

View on GitHub
 (11 comments) (4 reactions) (0 assignees)Go (802 forks)auto 404
help wantedtriage

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (Avg merge 14d 16h) (153 merged PRs in 30d)

Description

Description: Support for nested json access logs, which I believe envoy supports with the typed_json_format https://www.envoyproxy.io/docs/envoy/v1.33.0/configuration/observability/access_log/usage#format-dictionaries, would gives us the ability to follow GCP structured logging format: https://cloud.google.com/logging/docs/structured-logging#structured_logging_special_fields

Contributor guide

Research direction
Investigate the access log configuration in Envoy Gateway, specifically how the current JSON format is implemented. Understand the typed json format in Envoy and how to expose it through the Gateway API. Look at the existing code in the accesslog package and the translation logic to Envoy bootstrap configuration.
Tech stack
go
Domain
backendapiobservability
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoEnvoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50