apm: specify sampling bypass when discard_on_write_failure is false

Author: isaacaflores2

reference/apm/cloud/apm-settings.md

@@ -56,7 +56,7 @@ Some settings that could break your cluster if set incorrectly are blocklisted.
 ### Version 9.1+ [ec_version_9_1]
 
 `apm-server.sampling.tail.discard_on_write_failure`
-:   Defines the indexing behavior when trace events fail to be written to storage (e.g. when the storage limit is reached). When set to `false`, traces will be indexed, significantly increasing the indexing load. When set to `true`, traces will be discarded, there will be data loss potentially resulting in broken traces. The default is `false`. 
+:   Defines the indexing behavior when trace events fail to be written to storage (e.g. when the storage limit is reached). When set to `false`, traces will bypass sampling and always be indexed, significantly increasing the indexing load. When set to `true`, traces will be discarded, there will be data loss potentially resulting in broken traces. The default is `false`. 
 
 ### Version 8.0+ [ec_version_8_0_3]
 

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

@@ -80,7 +80,7 @@ Some settings that could break your cluster if set incorrectly are blocklisted.
 ### Version 9.1+ [ec_version_9_1]
 
 `apm-server.sampling.tail.discard_on_write_failure`
-:   Defines the indexing behavior when trace events fail to be written to storage (e.g. when the storage limit is reached). When set to `false`, traces will be indexed, significantly increasing the indexing load. When set to `true`, traces will be discarded, there will be data loss potentially resulting in broken traces. The default is `false`.
+:   Defines the indexing behavior when trace events fail to be written to storage (e.g. when the storage limit is reached). When set to `false`, traces will bypass sampling and always be indexed, significantly increasing the indexing load. When set to `true`, traces will be discarded, there will be data loss potentially resulting in broken traces. The default is `false`.
 
 ### Version 8.0+ [ec_version_8_0_3]
 

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

@@ -87,7 +87,7 @@ Policies map trace events to a sample rate. Each policy must specify a sample ra
 
 ### Discard On Write Failure [sampling-tail-discard-on-write-failure-ref]
 
-Defines the indexing behavior when trace events fail to be written to storage (e.g. when the storage limit is reached). When set to `false`, traces will be indexed, significantly increasing the indexing load. When set to `true`, traces will be discarded, there will be data loss potentially resulting in broken traces.
+Defines the indexing behavior when trace events fail to be written to storage (e.g. when the storage limit is reached). When set to `false`, traces will bypass sampling and always be indexed, significantly increasing the indexing load. When set to `true`, traces will be discarded, there will be data loss potentially resulting in broken traces. The default is `false`.
 
 Default: `false`. (bool)