Is your feature request related to a problem? Please describe.
User users FluentBit for access logging and currently the only way to get access log from Gloo is to write them to stdout. Since envoy does not support log rotation there could be issues with this approach if the logs are not maintained.
Describe the solution you'd like
Envoy has support for the fluentd protocol and it would be nice to configure Gloo to export logs directly to fluentbit.
Option with using sidecar container does not look good as this will require logs rotation and without customizing envoy images it would require killing existing pods every time we need to rotate logs.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Product
Enterprise
Gloo Edge Version
1.16
Is your feature request related to a problem? Please describe.
User users FluentBit for access logging and currently the only way to get access log from Gloo is to write them to stdout. Since envoy does not support log rotation there could be issues with this approach if the logs are not maintained.
Describe the solution you'd like
Envoy has support for the fluentd protocol and it would be nice to configure Gloo to export logs directly to fluentbit.
https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/access_loggers/fluentd/v3/fluentd.proto#envoy-v3-api-msg-exte[…]fluentdaccesslogconfig
Describe alternatives you've considered
Writing access logs to stdout
Option with using sidecar container does not look good as this will require logs rotation and without customizing envoy images it would require killing existing pods every time we need to rotate logs.
Additional Context
No response