Consul logging is not sufficient in our environment
During a recent failover production#637 (closed), consul is involved in healthchecking and allowing a node to register itself as part of the patroni cluster. If we experience some sort of failure with consul, we need to be able to look at the logs to assist in pointing fingers.
Instance patroni-01 has been rebooted since the aforementioned failover, and we no longer have logs related to consul from this node.
Use this issue to persist logs for all servers in our environment for the running consul service. For both clients and our consul servers we should be maintaining logs for a lengthy period of time to allow for sufficient investigation into potential issues with services, especially when we rely on said service for operation portions of our infrastructure.