Until now, a failure in transmitting access logs (e.g. a UNIX socket not responding/existing) would mean that Sōzu would not emit access logs anymore.
This pull request:
adds a revive_backend function
makes Sōzu startup impossible if the backend of access logs does not exist (note: if no access_logs_target is given in config.toml, it will still default to stdout)
Additionally, this PR adds error types and propagation.
Until now, a failure in transmitting access logs (e.g. a UNIX socket not responding/existing) would mean that Sōzu would not emit access logs anymore.
This pull request:
revive_backendfunctionaccess_logs_targetis given inconfig.toml, it will still default to stdout)Additionally, this PR adds error types and propagation.