Skip to content

Commit e3a4647

Browse files
authored
Update tail-based-sampling.md
1 parent 14c0566 commit e3a4647

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

solutions/observability/apps/tail-based-sampling.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -86,9 +86,13 @@ Policies map trace events to a sample rate. Each policy must specify a sample ra
8686

8787
The amount of storage space allocated for trace events matching tail sampling policies. Caution: Setting this limit higher than the allowed space may cause APM Server to become unhealthy.
8888

89-
If the configured storage limit is insufficient, it logs "configured storage limit reached". The event will bypass sampling and will always be indexed when storage limit is reached.
89+
A value of `0GB` (or equivalent) does not set a concrete limit, but rather allows the APM Server to align its disk usage with the disk size. APM server uses up to 80% of the disk size limit on the disk where the local tail-based sampling database is located. The last 20% of disk will not be used by APM Server. It is the recommended value as it automatically scales with the disk size.
9090

91-
Default: `3GB`. (text)
91+
If this is not desired, a concrete `GB` value can be set for the maximum amount of disk used for tail-based sampling.
92+
93+
If the configured storage limit is insufficient, it logs "configured limit reached". The event will bypass sampling and will always be indexed when storage limit is reached.
94+
95+
Default: `0GB`. (text)
9296

9397
| | |
9498
| --- | --- |

0 commit comments

Comments
 (0)