cf-charmers team mailing list archive

[Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>]

No, if it is deprecated we don't need to continue down that path. We need
to get packages moving again so we can track trunk cf-releases once again
and stay in-sync with the platform changes, like this one.

Thanks,
Ben

On Thu, Nov 20, 2014 at 8:54 AM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Hi, all.
>
> syslog_aggregator is taken away from cf-release since v192, you can see
> docs being updated [1] (here is a diff [2]). In the latest version of CF
> all component are equipped with metron agent that can stream logs as syslog
> to endpoint that you set in configuration [3]. The only thing you need
> specify in this case is `syslog_daemon_config` properties with address,
> port and protocol. This means that any logs monitor (both logstash and
> rsyslog) can use it. This approach requires having optional `syslog`
> relation for every CF component (I've wrote question about it already in
> this group [4]).
>
> Benjamin, regarding the fact syslog_aggregator is moved from cf-release,
> do you think it is actual task for me to investigate how it can be added to
> the charms.
>
>
> Best luck,
> Alex L.
>
> [1] http://docs.cloudfoundry.org/running/managing-cf/logging.html
> [2]
> https://github.com/cloudfoundry/docs-running-cf/commit/8be337668472d3a0e4909d9318a4e75ef7e12adf
> [3]
> https://github.com/cloudfoundry/loggregator/blob/develop/bosh/jobs/metron_agent/templates/syslog_forwarder.conf.erb#L52
> [4] https://lists.launchpad.net/cf-charmers/msg00630.html
>