Skip to content
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.

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

[8.8] docs: Add tail-based sampling common problem (backport #11662) #11681

Merged
merged 3 commits into from
Sep 25, 2023
Merged
Changes from all commits
Commits
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
11 changes: 11 additions & 0 deletions docs/common-problems.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ This section describes common problems you might encounter when using a Fleet-ma
* <<common-ssl-problems>>
* <<io-timeout>>
* <<field-limit-exceeded-legacy>>
* <<tail-based-sampling-memory-disk-io>>

[float]
[[no-data-indexed]]
Expand Down Expand Up @@ -187,3 +188,13 @@ In the agent logs, you won't see a sign of failures as the APM server asynchrono
----
{\"type\":\"illegal_argument_exception\",\"reason\":\"Limit of total fields [1000] in [INDEX_NAME] has been exceeded\"}
----

[[tail-based-sampling-memory-disk-io]]
[float]
=== Tail-based sampling causing high system memory usage and high disk IO

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,
please ensure that there is enough memory headroom in the system for OS page cache to perform disk IO efficiently.