Session recording mode selection creates inconsistent audit and storage behavior

Goal: determine the optimal session recording configuration for a low‑traffic Teleport deployment that uses the open‑source edition with local users.

Constraints: the choice between node‑level and proxy‑level recording, and between synchronous and asynchronous modes, influences audit completeness, storage cost, and behavior when OpenSSH clients connect directly to a node (bypassing the proxy). Asynchronous recording reduces auth‑server load but can lose recordings if a node fails before upload; synchronous mode guarantees durability but increases load. Node recording captures sessions even when the proxy is not involved, while proxy recording only sees proxied connections.

Questions: Which recording mode provides sufficient audit completeness for compliance while keeping storage usage minimal on a single‑node deployment? How does asynchronous node recording behave when an OpenSSH client connects directly to the node bypassing the proxy? What are the trade‑offs between proxy‑synchronous and node‑asynchronous recording in terms of durability and resource consumption for low‑traffic Teleport instances?