gravitational/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-10-12 02:15:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Reference doc updates (#67151)

Browse Source 
* docs: Reference doc updates

* docs: correct desktop.directory.write audit reference
This commit is contained in:
Steven Martin
2026-06-07 19:15:44 +00:00
committed by GitHub
parent 5c5723b188
commit 1ade712791
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages/enroll-resources/desktop-access/reference/audit.mdx
+2 -2
View File
@@ -225,7 +225,7 @@ that were sent.
## desktop.directory.write (TDP06I/W)
This event is part of the directory sharing feature, and is emitted when
Teleport reads writes from the remote desktop to a file on the user's local
Teleport writes from the remote desktop to a file on the user's local
machine.
In order to avoid capturing sensitive data, the event only records the offset
@@ -241,7 +241,7 @@ that were written.
"directory_id": 2,
"directory_name": "local-files",
"ei": 0,
"event": "desktop.directory.read",
"event": "desktop.directory.write",
"file_path": "powershell-scripts/a-script.ps1", // relative path from the root of the shared directory (local-files in this case)
"length": 734, // the number of bytes written
"offset": 0, // the offset from the start of the file from which the write began
docs/pages/reference/deployment/managed-updates-v2.mdx
+1 -1
View File
@@ -58,7 +58,7 @@ A single rollout is active at a time. Each Auth Service updates the rollout ever
Reports how many agents are connected to each auth, and which version they are running.
This is used to track update progress and automatically progress the rollout.
Each Teleport Auth Service instance generate one report evert minute.
Each Teleport Auth Service instance generates one report every minute.
Agents are counted in the report only if:
- they are connected for at least a minute
docs/pages/reference/deployment/scaling.mdx
+2 -2
View File
@@ -69,7 +69,7 @@ $ cat /proc/$(pidof teleport)/limits
## DynamoDB configuration
When using Teleport with DynamoDB, we recommend using on-demand provisioning.
This allow DynamoDB to scale with cluster load.
This allows DynamoDB to scale with cluster load.
For customers that can not use on-demand provisioning, we recommend at least
250 WCU and 100 RCU for 10k clusters.
@@ -128,7 +128,7 @@ has default limits of 4CPU and 4Gi memory.
Windows Desktop Service resource utilization can vary significantly based on workload, user behavior, and environment. For this reason it is challenging to provide absolute CPU and RAM requirements. This worked example is an illustration of one potential approach in determining the resource limits for a given Windows Desktop Service instance.
There are three primary factors that influence resource utilization by the Windows Desktop Service:
There are four primary factors that influence resource utilization by the Windows Desktop Service:
1. Number of concurrent sessions.
1. Number of registered desktops.
1. Screen update frequency per session.