7299 logging to file

[sheidkamp]

Adding the ability to log to a file instead of STDOUT by setting the LOG_TO_FILE_LOCATION environment variable. This is done to support AWS Fargate, which can not collect logs from STDOUT:

For pods running on Fargate, you need to use the sidecar pattern. You can run a Fluentd (or [Fluent Bit](http://fluentbit.io/)) sidecar container to capture logs produced by your applications. This option requires that the application writes logs to filesystem instead of stdout or stderr.

https://aws.amazon.com/blogs/containers/how-to-capture-application-logs-when-using-amazon-eks-on-aws-fargate/

[solo-changelog-bot[bot]]

Issues linked to changelog: https://github.com/solo-io/gloo/issues/7299

[elcasteel]

Do we have plans to add this to documentation?

[sheidkamp]

Do we have plans to add this to documentation?

Great question @elcasteel - Looking a a similar piece of functionality (SPLIT_LOG_OUTPUT), the only documentation I can find is in the changelogs.

Happy to update appropriate documentation, if we have a spot.

[elcasteel]

Do we have plans to add this to documentation?

Great question @elcasteel - Looking a a similar piece of functionality (SPLIT_LOG_OUTPUT), the only documentation I can find is in the changelogs.

Happy to update appropriate documentation, if we have a spot.

This is a bit of a gap for us right now. Perhaps we could add a note in a fargate related guide?

[sheidkamp]

/skip-changelog

[sheidkamp]

/skip-changelog

[sheidkamp]

/skip-changelog