Closed robertjsullivan closed 7 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/135730615
The labels on this github issue will be updated when the story is started.
Loggregator will close a "slow" connection and expect the client to reconnect. I have updated the README.md to reflect this.
cc @irabinovitch
https://github.com/cloudfoundry-incubator/datadog-firehose-nozzle#slowconsumeralert
We are using the nozzle to connect to the latest loggregator, and we are not seeing the slowConsumerAlert. Can you confirm that the two rules ( the TruncatingBuffer.DroppedMessages metric and the
1008
on disconnect) are still accurate?