search

projectcontour / contour-operator

Experimental repository to explore an operator for deploying Contour
Apache License 2.0
43 stars 34 forks source link

Envoy access log format #377

Open r0bj opened 3 years ago

r0bj commented 3 years ago

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.

danehans commented 3 years ago

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 commented 3 years ago

xref https://github.com/projectcontour/contour/pull/3694

r0bj commented 3 years ago

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