Open jstrachan opened 8 years ago
Without fluentd logging is missing something... logs. How about splitting out elasticsearch & kibana out into separate app & new app for pod logging which requires that?
Though lots of things an work with logs/ES - pipeline builds & deploys, git-collector & Apiman so far. Am sure we'll make more collectors too. (Eg hubot & issue tracker).
Maybe renaming 'logging' to something else might be less confusing. Can think of a good name get; 'Es-kibana'? Or 'eventing'?
On Saturday, 19 March 2016, Jimmi Dyson notifications@github.com wrote:
Without fluentd logging is missing something... logs. How about splitting out elasticsearch & kibana out into separate app & new app for pod logging which requires that?
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/fabric8io/fabric8/issues/5856#issuecomment-198736778
Red Hat
Twitter: @jstrachan Email: james.strachan@gmail.com Medium: https://medium.com/@jstrachan/ Blog: http://macstrac.blogspot.com/
fabric8: http:/ http://fusesource.com//fabric8.io/ hawtio: http:/ http://fusesource.com//hawt.io/
Open Source DevOps and Integration
daemonsets typically won't be able to be run by typical end users on kubernetes/openshift - its more of a sysadmin / ops thing.
So we should probably move the fluentd daemonset out of the logging app; so its just ES and kibana.
Then folks can manually run the daemonset via the command line (& we can continue to install it by default maybe in the Vagrantfile?)