From 65014e23c7c2fa8116626313c065793d9a25d6db Mon Sep 17 00:00:00 2001 From: Carson Ip Date: Fri, 25 Apr 2025 19:22:05 +0100 Subject: [PATCH] apm: remove TBS high RSS common problem --- troubleshoot/observability/apm/common-problems.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/troubleshoot/observability/apm/common-problems.md b/troubleshoot/observability/apm/common-problems.md index ec8e1eb94d..24e55ad538 100644 --- a/troubleshoot/observability/apm/common-problems.md +++ b/troubleshoot/observability/apm/common-problems.md @@ -18,7 +18,6 @@ This section describes common problems you might encounter when using APM Server * [Common SSL-related problems](#apm-common-ssl-problems) * [I/O Timeout](#apm-io-timeout) * [Field limit exceeded](#apm-field-limit-exceeded) -* [Tail-based sampling causing high system memory usage and high disk IO](#apm-tail-based-sampling-memory-disk-io) **Applications UI**: @@ -180,14 +179,6 @@ In the agent logs, you won’t see a sign of failures as the APM server asynchro ``` -## Tail-based sampling causing high system memory usage and high disk IO [apm-tail-based-sampling-memory-disk-io] -```yaml {applies_to} -stack: all -``` - -Tail-based sampling requires minimal memory to run, and there should not be a noticeable increase in RSS memory usage. However, since tail-based sampling writes data to disk, it is possible to see a significant increase in OS page cache memory usage due to disk IO. If you see a drop in throughput and excessive disk activity after enabling tail-based sampling, ensure that there is enough memory headroom in the system for OS page cache to perform disk IO efficiently. - - ## Too many unique transaction names [troubleshooting-too-many-transactions] ```yaml {applies_to} stack: all