Hi Guangcai, The log messages are coming from the syslog_drain_binder process which is colocated with dopplers. The syslog_drain_binder is used to poll the CloudController for active syslog drain URLs

The noaa library also lets you consume data from the loggregator firehose. The firehose sample app <https://github.com/cloudfoundry/noaa/blob/master/firehose_sample/main.go> shows how you can do this.

Answers to your questions: 1. That error might be caused if your doppler servers aren't healthy and therefore not listed in etcd. The traffic-controller polls etcd to discover dopplers. 2. You do need

Hi Marco, We instrumented the collector and found that none of the existing CF components provide any tags which would be overridden by the latest collector change. So this change shouldn't affect any

Correct, the datadog-firehose-nozzle has its own custom client which makes REST calls to the datadog API. It doesn't use the datadog statsd agent. A similar approach should work for you. Thanks, Rohit