Merge pull request #1686 from fluent/alexakreizinger/sc-136424/misc-remove-more-unused-files-images-from

Author: alexakreizinger

imgs/processor_opentelemetry_envelope.png renamed to .gitbook/assets/processor_opentelemetry_envelope.png

@@ -354,7 +354,7 @@ name:
 You can create Grafana dashboards and alerts using Fluent Bit's exposed Prometheus
 style metrics.
 
-The provided [example dashboard](https://github.com/fluent/fluent-bit-docs/tree/8172a24d278539a1420036a9434e9f56d987a040/monitoring/dashboard.json)
+The provided [example dashboard](https://github.com/fluent/fluent-bit-docs/blob/master/monitoring/dashboard.json)
 is heavily inspired by [Banzai Cloud](https://banzaicloud.com)'s
 [logging operator dashboard](https://grafana.com/grafana/dashboards/7752) with a few
 key differences, such as the use of the `instance` label, stacked graphs, and a focus
@@ -366,7 +366,7 @@ for more information.
 
 ### Alerts
 
-Sample alerts are available [here](https://github.com/fluent/fluent-bit-docs/tree/8172a24d278539a1420036a9434e9f56d987a040/monitoring/alerts.yaml).
+Sample alerts are available [here](https://github.com/fluent/fluent-bit-docs/blob/master/monitoring/alerts.yaml).
 
 ## Health Check for Fluent Bit
 

imgs/traces_head_sampling.png renamed to .gitbook/assets/traces_head_sampling.png

@@ -2,7 +2,7 @@
 
 The _OpenTelemetry Envelope_ processor is used to transform your data to be compatible with the OpenTelemetry Log schema. If your data was __not__ generated by [OpenTelemetry input](../inputs/opentelemetry.md) and your backend or destination for your logs expects to be in an OpenTelemetry schema.
 
-![](/imgs/processor_opentelemetry_envelope.png)
+![](../.gitbook/assets/processor_opentelemetry_envelope.png)
 
 ## Configuration Parameters
 

imgs/traces_tail_sampling.png renamed to .gitbook/assets/traces_tail_sampling.png

@@ -34,7 +34,7 @@ Sampling has both a name and a type with the following possible settings:
 
 In this example, head sampling will be used to process a smaller percentage of the overall ingested traces and spans. This is done by setting up the pipeline to ingest on the OpenTelemetry defined port as shown below using the OpenTelemetry Protocol (OTLP). The processor section defines traces for head sampling and the sampling percentage defining the total ingested traces and spans to be forwarded to the defined output plugins.
 
-![](/imgs/traces_head_sampling.png)
+![](../.gitbook/assets/traces_head_sampling.png)
 
 | Sampling settings     | Description                                                                                                         |
 | :-------------------- | :------------------------------------------------------------------------------------------------------------------ |
@@ -72,7 +72,7 @@ With this head sampling configuration, a sample set of ingested traces will rand
 
 Tail sampling is used to obtain a more selective and fine grained control over the collection of traces and spans without collecting everything. Below is an example showing the process is a combination of waiting on making a sampling decision together followed by configuration defined conditions to determine the spans to be sampled.
 
-![](/imgs/traces_tail_sampling.png)
+![](../.gitbook/assets/traces_tail_sampling.png)
 
 The following samplings settings are available with their default values: