Skip to content

apm: remove TBS high RSS common problem #1268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

apm: remove TBS high RSS common problem #1268

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions troubleshoot/observability/apm/common-problems.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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**:

Expand Down Expand Up @@ -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
Expand Down
Loading