Previous alerts in two ways:
the nozzle receives a WebSocket close error with error code ClosePolicyViolation (1008)
the nozzle receives a CounterEvent with the name TruncatingBuffer.DroppedMessages
The latest document has changed to:
If a nozzle falls behind, Loggregator alerts the nozzle in two ways:
TruncatingBuffer alerts: If the nozzle consumes messages more slowly than they are produced, the Loggregator system may drop messages. In this case, Loggregator sends the log message, TB: Output channel too full. Dropped N messages, where N is the number of dropped messages. Loggregator also emits a CounterEvent with the name doppler_proxy.slow_consumer. The nozzle receives both messages from the Firehose, alerting the operator to the performance issue.
Previous alerts in two ways: the nozzle receives a WebSocket close error with error code ClosePolicyViolation (1008) the nozzle receives a CounterEvent with the name TruncatingBuffer.DroppedMessages
The latest document has changed to: If a nozzle falls behind, Loggregator alerts the nozzle in two ways: TruncatingBuffer alerts: If the nozzle consumes messages more slowly than they are produced, the Loggregator system may drop messages. In this case, Loggregator sends the log message, TB: Output channel too full. Dropped N messages, where N is the number of dropped messages. Loggregator also emits a CounterEvent with the name doppler_proxy.slow_consumer. The nozzle receives both messages from the Firehose, alerting the operator to the performance issue.