Validate OTLP Endpoint #1106
Labels
area/metrics
MetricPipeline
area/traces
TracePipeline
kind/bug
Categorizes issue or PR as related to a bug.
Milestone
Description
Recent changes to the OpenTelemetry collector may terminate the Collector ungracefully in the case of a malformed OTLP endpoint.
Expected result
An endpoint value in a MetricPipeline or TracePipeline should never result in a crashing Pod. If the user defines a value that will not be accepted by the Collector, the configuration should not be applied and the problem indicated in the pipeline status.
Ensure that pipeline validation logic is not duplicated in the individual reconcilers
Actual result
When a user defines such an endpoint in a MetricPipeline or TracePipeline, this results in a crashing pod. In older releases of the Collector, it was running but not shipping any data.
Steps to reproduce
Create a MetricPipeline with endpoint that does not have a port. E.g., set the value to
/
. The exact values that are accepted by the Collector have to be evaluated.Troubleshooting
Release Notes
Similar but different ticket: #1106
The text was updated successfully, but these errors were encountered: