Skip to content
This repository has been archived by the owner on Feb 27, 2023. It is now read-only.

Envoy access log format #377

Open
r0bj opened this issue Jun 2, 2021 · 3 comments
Open

Envoy access log format #377

r0bj opened this issue Jun 2, 2021 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@r0bj
Copy link

r0bj commented Jun 2, 2021

Please describe the problem you have
[A clear, concise, description of the problem you are facing. What is the problem that feature X would solve for you?]

Is ConfigMap contour designed to be edited by human operators or it will be overwrite by contour operator?

If ConfigMap contour is not designed to be edited by human operator It would be useful to be able to configure access log format from operator CRD level.

@r0bj r0bj added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 2, 2021
@danehans
Copy link
Contributor

Is ConfigMap contour designed to be edited by human operators or it will be overwrite by contour operator?

The configmap is meant to be managed by the operator.

If ConfigMap contour is not designed to be edited by human operator It would be useful to be able to configure access log format from operator CRD level.

Ack. Let us know if you have any specific logging requirements that should be considered.

xref: https://projectcontour.io/guides/structured-logs/
xref: https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/access_log/usage

@skriss
Copy link
Member

skriss commented Jun 14, 2021

xref projectcontour/contour#3694

@r0bj
Copy link
Author

r0bj commented Jul 11, 2021

In my use case, I would like to use JSON as a access log format to be easily consumed by log aggregator.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants