Details
Description
We've got this:
ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a] OPEN ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a] BOUND: 0.0.0.0/0.0.0.0:37250 ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a, 0.0.0.0/0.0.0.0:37250 => /226.1.1.3:60100] CONNECTED: /226.1.1.3:60100 ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a, 0.0.0.0/0.0.0.0:37250 => /226.1.1.3:60100] WRITTEN_AMOUNT: 129 ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a, 0.0.0.0/0.0.0.0:37250 :> /226.1.1.3:60100] DISCONNECTED ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a, 0.0.0.0/0.0.0.0:37250 :> /226.1.1.3:60100] UNBOUND ATTENTION: The pipeline contains no upstream handlers; discarding: [id: 0x1f79354a, 0.0.0.0/0.0.0.0:37250 :> /226.1.1.3:60100] CLOSED
We can fix this by adding an upstream handler that discards the message without printing them.