-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow configuring envoy's application log format for better integration with observability tooling #7214
Comments
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
|
it's in https://app.datadoghq.com/logs/pipelines -> name -> kuma-cp > steps 1 & 2 |
Automatically closing the issue due to having one of the "closed state label". |
Description
It would be beneficial to allow configuring envoy application logging format (probably json would be enough), which would allow better integration with observability tooling (like Datadog)
ref. https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/application_logging#printing-logs-in-json-format
The text was updated successfully, but these errors were encountered: