You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When the same receiver is referenced in more than one pipeline, the Collector creates only one receiver instance at runtime that sends the data to a fan-out consumer. The fan-out consumer in turn sends the data to the first processor of each pipeline. The data propagation from receiver to the fan-out consumer and then to processors is completed using a synchronous function call. This means that if one processor blocks the call, the other pipelines attached to this receiver are blocked from receiving the same data, and the receiver itself stops processing and forwarding newly received data.
Describe the solution you'd like
Want to reproduce the scenario
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
When a receiver is referenced in multiple pipelines, OpenTelemetry Collector creates a single receiver instance that fans out data to all attached pipelines synchronously. If a processor in one pipeline blocks execution, it prevents data propagation to other pipelines and stops the receiver from processing new incoming data.
how can i configure telemetry collector to block execution of a processor,
Component(s)
No response
Is your feature request related to a problem? Please describe.
When the same receiver is referenced in more than one pipeline, the Collector creates only one receiver instance at runtime that sends the data to a fan-out consumer. The fan-out consumer in turn sends the data to the first processor of each pipeline. The data propagation from receiver to the fan-out consumer and then to processors is completed using a synchronous function call. This means that if one processor blocks the call, the other pipelines attached to this receiver are blocked from receiving the same data, and the receiver itself stops processing and forwarding newly received data.
Describe the solution you'd like
Want to reproduce the scenario
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: