Formatting and changelog

Signed-off-by: Matej Gera <[email protected]>

otel-integration/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## OpenTelemtry-Integration
 
+### v0.0.50 / 2024-01-18
+
+- [FEAT] Add global metric collection interval
+- [FIX] Suppress generation of `service.name` from collector telemetry.
+
 ### v0.0.49 / 2024-01-18
 
 - [CHORE] Update Windows collector image to `v0.92.0`.

otel-integration/k8s-helm/README.md

@@ -255,7 +255,9 @@ env:
 
 ### About global collection interval
 
-The global collection interval (`global.collectionInterval`) is the interval in which the collector will collect metrics from the configured receivers. For most optimal default experience, we recommend using the 30 second interval set by the chart. However, if you'd prefer to collect metrics more (or less) often, you can adjust the interval by changing the `global.collectionInterval` value in the `values.yaml` file. The minimal recommended global interval is `15s`. If you wish to use default value for _each_ component set internally by the collector, you can remove the collection interval parameter from presets completely. Beware that using lower interval will result in more metric data points being sent to the backend, thus resulting in more costs. Note that the choise of the interval also has an effect on behavior of rate functions, for more see [here](https://www.robustperception.io/what-range-should-i-use-with-rate/).
+The global collection interval (`global.collectionInterval`) is the interval in which the collector will collect metrics from the configured receivers. For most optimal default experience, we recommend using the 30 second interval set by the chart. However, if you'd prefer to collect metrics more (or less) often, you can adjust the interval by changing the `global.collectionInterval` value in the `values.yaml` file. The minimal recommended global interval is `15s`. If you wish to use default value for _each_ component set internally by the collector, you can remove the collection interval parameter from presets completely. 
+
+Beware that using lower interval will result in more metric data points being sent to the backend, thus resulting in more costs. Note that the choise of the interval also has an effect on behavior of rate functions, for more see [here](https://www.robustperception.io/what-range-should-i-use-with-rate/).
 
 ### About span metrics