Hello Cloudfoundry developers,
Recently, my colleague and I shared at a local meetup
about our approach to persisting the application logs for the users of
our Cloudfoundry setup.
http://www.slideshare.net/rakutentech/fluentd-meetup-logging-infrastructure-in-paa-s
We had do work this out so that we could enable the users
to have log archives from their applications running in production,
as well as to make it easier to debug for them during development.
For this purpose, we mostly relied on a log collector named Fluentd
and attach it to an instance on startup.
The current implementation is relatively straightforward and can be seen here:
https://github.com/rakutentech/dea/commit/64d271904de1e195cc90ca1958eadf704f530d94
In terms of the Cloudfoundry roadmap, how would the problem of persisting the
logs from a user be solved? I understand that touching the deployment pipeline
is a delicate issue so, what would be a guideline to follow so that we
can contribute back
something like this to the community?
Cloudfoundry has improved a lot the development life of our developers,
so we would really like to contribute if possible.
Thanks again for Cloudfoundry!
- Wally