Question 1
IntermediateGet Metrics In with OpenTelemetry · Configure the OTel Collector
While reviewing /etc/otel/collector/agent_config.yaml on a Linux host, a platform engineer needs to route incoming trace spans through a first pipeline to extract span metrics and then feed those generated metrics directly into a second metrics pipeline within the same Splunk Distribution of the OpenTelemetry Collector instance. The engineer also needs to ensure the health_check extension is active.
Which Collector component type acts simultaneously as an exporter at the end of the first pipeline and as a receiver at the beginning of the second pipeline, and where must health_check be enabled?
Answer and explanation
Correct answer: C
In the Splunk Distribution of the OpenTelemetry Collector, a Connector links two pipelines by acting as an exporter at the end of the first pipeline and as a receiver at the beginning of the second pipeline. The service section contains two primary elements: extensions (a list of enabled optional capabilities such as health_check) and pipelines (which link receivers, processors, and exporters). Extensions are never placed inside individual pipelines under service.pipelines, and processors only modify telemetry within a pipeline rather than bridging two separate pipelines.
