Skip to content

Commit 201df71

Browse files
Apply suggestions to align with recent changes to the docs
Co-authored-by: Carson Ip <[email protected]>
1 parent 7041c81 commit 201df71

File tree

3 files changed

+2
-13
lines changed

3 files changed

+2
-13
lines changed

reference/apm/cloud/apm-settings.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -53,11 +53,6 @@ If a setting is not supported by {{ech}}, you will get an error message when you
5353
Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](/solutions/observability/apm/configure-apm-server.md).
5454
::::
5555

56-
### Version 9.1+ [ec_version_9_1]
57-
This {{stack}} version adds support for the following settings:
58-
59-
`apm-server.sampling.tail.discard_on_write_failure`
60-
: Defines the indexing behavior when trace events fail to be written to storage (for example, when the storage limit is reached). When set to `false`, traces bypass sampling and are always indexed, which significantly increases the indexing load. When set to `true`, traces are discarded, causing data loss which can result in broken traces. The default is `false`.
6156

6257
### Version 8.0+ [ec_version_8_0_3]
6358

solutions/observability/apm/configure-apm-server.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -77,12 +77,6 @@ If a setting is not supported on {{ecloud}}, you will get an error message when
7777
Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](/solutions/observability/apm/configure-apm-server.md).
7878
::::
7979

80-
### Version 9.1+ [ec_version_9_1]
81-
This {{stack}} version adds support for the following settings:
82-
83-
`apm-server.sampling.tail.discard_on_write_failure`
84-
: Defines the indexing behavior when trace events fail to be written to storage (for example, when the storage limit is reached). When set to `false`, traces bypass sampling and are always indexed, which significantly increases the indexing load. When set to `true`, traces are discarded, causing data loss which can result in broken traces. The default is `false`.
85-
8680
### Version 8.0+ [ec_version_8_0_3]
8781

8882
This stack version removes support for some previously supported settings. These are all of the supported settings for this version:

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,8 @@ Default: `false`. (bool)
9393

9494
| | |
9595
|------------------------------|------------------------------------------|
96-
| APM Server binary | `sampling.tail.discard_on_write_failure` |
97-
| Fleet-managed (version 9.1+) | `Discard On Write Failure` |
96+
| APM Server binary | `apm-server.sampling.tail.discard_on_write_failure` |
97+
| Fleet-managed {applies_to}`stack: ga 9.1` | `Discard On Write Failure` |
9898

9999

100100
### Storage limit [sampling-tail-storage_limit-ref]

0 commit comments

Comments
 (0)