Syslog drain binder job being replaced by cf-syslog-drain release


Adam Hevenor
 

Hi All -

In the next few packages of cf-release we are going to be introducing a new release called cf-syslog-drain release [1]. This release handles this functionality and was proposed as the Scalable Syslog feature proposal [2]. Properties for drain specific functionality like blacklisting will be moving to this new release. Specific mapping of these properties will be documented in a future version of cf-release notes. This release is also already available in cf-deployment with the experimental operations file titled disable-etcd.

Thanks
Adam

[1] - http://bosh.io/releases/github.com/cloudfoundry/cf-syslog-drain-release?all=1
[2] - https://docs.google.com/document/d/1B31BWuPVGYIbQaEVfFhmTmp8_5t8RwGGHY_4q4unojI/edit


Mike Youngstrom <youngm@...>
 

Great! Do you have a timeline for removal of the old syslog
functionality? Some of our loggregator syslog integrations are not
compatible with the new release. If the old functionality could remain in
place for a couple of months after the complete integration of the new
syslog drain that would be optimal.

Thanks,
Mike

On Mon, Sep 11, 2017 at 12:01 PM, Adam Hevenor <ahevenor(a)pivotal.io> wrote:

Hi All -

In the next few packages of cf-release we are going to be introducing a
new release called cf-syslog-drain release [1]. This release handles this
functionality and was proposed as the Scalable Syslog feature proposal [2].
Properties for drain specific functionality like blacklisting will be
moving to this new release. Specific mapping of these properties will be
documented in a future version of cf-release notes. This release is also
already available in cf-deployment with the experimental operations file
titled disable-etcd.

Thanks
Adam

[1] - http://bosh.io/releases/github.com/cloudfoundry/cf-
syslog-drain-release?all=1
[2] - https://docs.google.com/document/d/1B31BWuPVGYIbQaEVfFhmTmp8_
5t8RwGGHY_4q4unojI/edit


Altenhofen, Michael <michael.altenhofen@...>
 

Hi Adam,

sorry to nag you again (see [1]) with this, but will that release then implement the existing reconnection logic?

Thanks

Michael

[1] https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/message/FSD2FITNMDHSIB2ZB2QV2GZMOJTHOV44/

Am 11.09.17, 20:05 schrieb "Adam Hevenor" <ahevenor(a)pivotal.io>:

Hi All -

In the next few packages of cf-release we are going to be introducing a new release called cf-syslog-drain release [1]. This release handles this functionality and was proposed as the Scalable Syslog feature proposal [2]. Properties for drain specific functionality like blacklisting will be moving to this new release. Specific mapping of these properties will be documented in a future version of cf-release notes. This release is also already available in cf-deployment with the experimental operations file titled disable-etcd.

Thanks
Adam

[1] - http://bosh.io/releases/github.com/cloudfoundry/cf-syslog-drain-release?all=1
[2] - https://docs.google.com/document/d/1B31BWuPVGYIbQaEVfFhmTmp8_5t8RwGGHY_4q4unojI/edit