Closed mrsauravsahu closed 2 months ago
This update primarily introduces a configuration change to the OpenTelemetry Collector by adding a replicaCount
field set to zero and disabling metrics collection by setting metrics
to null
under service.pipelines
.
File Path | Change Summary |
---|---|
.../opentelemetry-collector/values.yaml |
Introduced replicaCount with a value of 0; Set metrics under service.pipelines to null . |
🐰✨ In the land of code, where data streams flow, A change has been made, with zero in tow. No metrics to gather, nowhere to go, Silent collectors, as quiet as snow. 🌟🌿
molecules/cluster-resources/config/externals/opentelemetry-collector/values.yaml (2)
`5-5`: Setting `replicaCount` to 0 effectively disables the standalone OTEL collector, aligning with the shift to a sidecar deployment model. --- `37-37`: Setting `metrics` to `null` under `service.pipelines` supports the transition to a sidecar model. Ensure this change does not inadvertently disable necessary functionality elsewhere.Verification successful
--- The review of the change in `molecules/cluster-resources/config/externals/opentelemetry-collector/values.yaml` where `metrics` is set to `null` has been analyzed. The search across other `values.yaml` files indicates that the `metrics` configurations in those files are specific to their respective services and do not appear to be directly related to the `opentelemetry-collector` configuration. Therefore, it is unlikely that this change will inadvertently disable necessary functionality in other services. - `molecules/cluster-resources/config/externals/rabbitmq/values.yaml` and other files show service-specific `metrics` configurations, unrelated to the `opentelemetry-collector`.Scripts Executed
The following scripts were executed for the analysis: --- Script: ```shell #!/bin/bash # Search for any references to the `metrics` pipeline in other configurations to ensure no unintended impacts. rg --type yaml 'metrics:' --glob '*values.yaml' ``` Length of output: 1537
Summary by CodeRabbit