Hello All, The firehose-plugin (cf nozzle) has been moved to http://github.com/cloudfoundry-community/firehose-plugin. The original repo in cloudfoundry github org will be deleted. For whatever reason

Hey cf-dev, The firehose-plugin repo <https://github.com/cloudfoundry/firehose-plugin> will be moving from the cloudfoundry github org to cloudfoundry-community github org in the upcoming weeks. The f

Hey cf-dev, This is just a notice to let everyone know that loggregator components now default the *pprof_port* to *0* from the defaults of 6060 and 6061. We are doing this in order to avoid port coll

Hey cf-dev, This is just a reminder to everyone. We bumped the gRPC work for loggregator into cf-release/develop. We now require certs for doppler and traffic controller. You can read about it in our

Hello cf-dev/cf-eng, Loggregator would like to notify the community of a change in behavior for noaa <https://github.com/cloudfoundry/noaa>, the client library for Loggregator. noaa <https://github.co

Hey cf-dev, Loggregator Consumer <https://github.com/cloudfoundry/loggregator_consumer> has been deprecated and is no longer supported. Loggregator Consumer is a library that allows an application dev

Hello cf-dev, Loggregator has been working on some improvements to the NOAA library. The recommended way to create a NOAA consumer is now consumer.New(...) under the consumer package instead of the le

Metron reads the doppler addresses from etcd. Each doppler advertises its address to etcd. Increasing the number of doppler instances will automatically spread the load from all the metrons over all t

You can obtain the "Authorization: bearer" token using the cf cli. cf login cf oauth-token

Hey CF-Dev, We are making the following changes to the Dropsonde interface library used by GoRouter to handle managing http headers to build the HttpStartStop event: - We replaced the X-CF-RequestID w

Thanks Amit. This might solve our problem. We are seeing problems deploying diego-release on bosh-lite with stemcell 3126.

Hey Parthiban, It seems that there may be a misconfiguration in your manifest. Did you configure the nfs_server properties? https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml

Try ssh'ing onto the box to see what the logs say. `bosh ssh api_z1 0` Then, `cd /var/vcap/sys/log/` There are plenty of logs to look through, I'd start by running `monit summary` (make sure to be roo

Hey Masumi, We setup a similar environment with CFv212 and went through a few scenarios. We took a look at the problem and we feel that there are couple of odd things. "Error when polling cloud contro

Hey Masumi, The LAMB team created a chore to investigate this here https://www.pivotaltracker.com/story/show/106699398. We'll update this thread with our findings. Thanks. Warren

Loggregator doesn't store any logs. The most it does is maintain a buffer as mentioned above which is defaulted to 100 lines of logs. If you wish to store logs you can forward them to third-party sysl

For #3, The Loggregator team currently doesn't manage the cf-java-client library. There seems to be another post in the community here (https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.clou

Hi Ponraj, For #1 The guid that gets printed out is the boundary for the multi-part message. When we serve the recent logs we create a multipart writer here(https://github.com/cloudfoundry/loggregator

Hi Ponraj, I've replicated the behavior you are seeing. I'll get back to you for question #1 and #2 after some investigation. As for #3 set your DOPPLER_ADDR to wss://doppler.xx.xxx.xxxxxxxx.xxx:443.

Hi Ponraj, It could be that your token may have expired. Also, silly question but you may want to check that you have access to the app in question. A good way to verify this is by running `cf logs <y