Deprecation of cf-syslog-drain-release
Jesse Weaver
As previously announced [1], the Loggregator team has developed a new way to forward application logs over syslog using agents, rather than centralized adapters. This new approach can scale to higher log volume and numbers of app drains, and allows log egress from CloudFoundry without any dependence on the Loggregator firehose.
We have had an ops file[2] to switch to this new architecture in cf-deployment for some time, and are working to make it the default in a coming major version of cf-deployment. This would mean the removal of the scalable-syslog architecture, with its schedulers and adapters, and the cf-syslog-drain release.
Once this has been released, we would like to mark the cf-syslog-drain release as deprecated, and halt development.
Please let us know if you have any concerns or questions.
We have had an ops file[2] to switch to this new architecture in cf-deployment for some time, and are working to make it the default in a coming major version of cf-deployment. This would mean the removal of the scalable-syslog architecture, with its schedulers and adapters, and the cf-syslog-drain release.
Once this has been released, we would like to mark the cf-syslog-drain release as deprecated, and halt development.
Please let us know if you have any concerns or questions.