Closed patsevanton closed 2 months ago
This issue is currently awaiting triage.
If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
I have helm chart with JSON logging. Values:
controller:
config:
log-format-escape-json: "true"
log-format-upstream: '{"time": "$time_iso8601", "remote_addr": "$proxy_protocol_addr", "x_forwarded_for": "$proxy_add_x_forwarded_for", "request_id": "$req_id",
"remote_user": "$remote_user", "bytes_sent": $bytes_sent, "request_time": $request_time, "status": $status, "vhost": "$host", "request_proto": "$server_protocol",
"path": "$uri", "request_query": "$args", "request_length": $request_length, "duration": $request_time,"method": "$request_method", "http_referrer": "$http_referer",
"http_user_agent": "$http_user_agent" }'
But could enable JSON loggin without set log-format-upstream ? For example:
controller:
config:
log-format-escape-json: "true"
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev
on Kubernetes Slack.
@longwuyuan: Closing this issue.
Hello! Thanks for Ingress-Nginx.
JSON logging pod by simple rule. For example:
Users who want use json logging set logFormat: json
Is there currently another issue associated with this? No Does it require a particular kubernetes version? No If this is actually about documentation, uncomment the following block No