cf-charmers team mailing list archive

[Manuel Garcia <mgarciap@xxxxxxxxx>]

Revisited Goals
1 - Aggregate CF infrastructure logs
Postpone CF Firehouse until it is more mature and used by the community.
Instead, use already existing  syslog_agregator [2] and drain logs to ELK [1]. syslog_aggregator is included in CF juju charms, but there is no options to turn it on yet. Alex will follow this up with Canonical.

This approach will allow us to have a working solution much faster.

We also talk about metrics. CF Collector component is included in the CF Bundle. We’ll revisit this item after next POC.

2 - Aggregate Applications Logs
Create a HowTo using a simple example app running on CF draining logs to ELK (deployed with Juju)
Provide something similar to what is documented in Cloudfoundry docs for Papertrail, SplunkStorm, etc [3] but for ELK Juju Bundle

Here is a hangout chat log https://gist.github.com/allomov/45e30054a2fdb4d9d66d

[1] https://gist.github.com/whitmo/0afeda827efe31240bcd
[2] http://docs.cloudfoundry.org/running/managing-cf/logging.html
[3] http://docs.cloudfoundry.org/devguide/services/log-management-thirdparty-svc.html



We haven’t talked about the CF Web Admin Console. Could someone share the roadmap and if it affects the Charm developed by Alex?

Thank you again for your time.

Manuel