Change to name Sampling instead of Traces in documentation. Fixes #1618. (#1619)

* Change to name Sampling instead of Traces in documentation. Fixes issue #1618.

Signed-off-by: Eric D. Schabell <[email protected]>

* Fixed list items to use star and not dash.

Signed-off-by: Eric D. Schabell <[email protected]>

---------

Signed-off-by: Eric D. Schabell <[email protected]>

Author: eschabell

SUMMARY.md

@@ -146,8 +146,8 @@
   * [Labels](pipeline/processors/labels.md)
   * [Metrics Selector](pipeline/processors/metrics-selector.md)
   * [OpenTelemetry Envelope](pipeline/processors/opentelemetry-envelope.md)
+  * [Sampling](pipeline/processors/sampling.md)
   * [SQL](pipeline/processors/sql.md)
-  * [Traces](pipeline/processors/traces.md)
   * [Filters as processors](pipeline/processors/filters.md)
   * [Conditional processing](pipeline/processors/conditional-processing.md)
 * [Filters](pipeline/filters/README.md)

pipeline/processors/README.md

@@ -18,9 +18,9 @@ Fluent Bit offers the following processors:
 - [Metrics Selector](metrics-selector.md): Choose which metrics to keep or discard.
 - [OpenTelemetry Envelope](opentelemetry-envelope.md): Transform logs into an
   OpenTelemetry-compatible format.
-- [SQL](sql.md): Use SQL queries to extract log content.
-- [Traces](traces.md): Trace sampling designed with a pluggable architecture,
+- [Sampling](sampling.md): Trace sampling designed with a pluggable architecture,
   allowing easy extension to support multiple sampling strategies and backends.
+- [SQL](sql.md): Use SQL queries to extract log content.
 - [Filters](filters.md): Any filter can be used as a processor.
 
 ## Features

pipeline/processors/traces.md renamed to pipeline/processors/sampling.md

@@ -1,6 +1,6 @@
-# Traces
+# Sampling
 
-The _Traces_ sampling processor is designed with a pluggable architecture, allowing easy extension to support multiple sampling strategies and backends. It provides you with the ability to apply head or tail sampling to incoming trace telemetry data.
+The _Sampling_ processor is designed with a pluggable architecture, allowing easy extension to support multiple trace sampling strategies and backends. It provides you with the ability to apply head or tail sampling to incoming trace telemetry data.
 
 Available samplers:
 
@@ -21,9 +21,9 @@ Conditions:
 
 The processor does not provide any extra configuration parameter, it can be used directly in your _processors_ Yaml directive.
 
-## Traces types
+## Sampling types
 
-Traces have both a name and a type with the following possible settings:
+Sampling has both a name and a type with the following possible settings:
 
 | Key    |     Possible values     |
 | :----- | :---------------------: |