You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Thales, Teleport supports multiple different persistence & logging backends (local filesystem, Dynamo/S3, etcd, etc) and each has its own unique requirements & tooling when it comes to deployment, backup, rotation, archival, sizing, etc. Part of what makes Teleport special is that it follows the unix philosophy of doing one thing and doing it really well (eg, enforcement of certificate-based identity at an encrypted protocol level). So what precisely you could or should do with the audit log or individual session recordings captured by Teleport is a highly personal or environment-specific concern that the Teleport feature set does not get into. (With regard to "recording feature" -- Teleport does have some options, such as configuration flag to do recording at all, to do recording at the teleport-node level or to run an entire cluster in "Recording Proxy" mode aka at a transparent MITM) But Teleport's feature set doesn't get into file or database management. With regard to max size, there may be ways to simply limit the length/time of sessions, which could indirectly approximate "size." Does that help?
What happened:
I would like to know where I can configure the recording feature (rotation, max size, etc)
What you expected to happen:
I expected to set these feature, or to find documentation around that.
Environment:
teleport version
): Teleport v2.7.4 git:v2.7.4-0-g2fff1056tsh version
): Teleport v2.7.4 git:v2.7.4-0-g2fff1056Browser environment
The text was updated successfully, but these errors were encountered: