On 10.05.2017 23:41, Dan Prince wrote: > On Mon, 2017-04-24 at 07:47 -0400, Joe Talerico wrote: >> Hey owls - I have been playing with oslo.log fluentd integration[1] >> in >> a poc commit here [2]. Enabling the native service logging is nice >> and >> tracebacks no longer multiple inserts into elastic - there is a >> "traceback" key which would contain the traceback if there was one. >> >> The system-level / kernel level logging is still needed with the >> fluent client on each Overcloud node. >> >> I see Martin did the initial work [3] to integrate fluentd, is there >> anyone looking at migrating the OpenStack services to using the >> oslo.log facility? > > Nobody officially implementing this yet that I know of. But it does > look promising. > > The idea of using oslo.logs fluentd formatter could dovetail very > nicely into our new containers (docker) servers for Pike in that it > would allow us to log to stdout directly within the container... but > still support the Fluentd logging interfaces that we have today. > > The only downside would be that not all services in OpenStack support > olso.log (I don't think Swift does for example). Nor do some of the > core services we deploy like Galera and RabbitMQ. So we'd have a mixed > bag of host and stdout logging perhaps for some things or would need to > integrate with Fluentd differently for services without oslo.log > support. > > Our current approach to containers logging in TripleO recently landed > here and exposed the logs to a directory on the host specifically so > that we could aim to support Fluentd integrations: > > https://review.openstack.org/#/c/442603/ > > Perhaps we should revisit this in the (near) future to improve our > containers deployments. > > Dan >
Note, the aforementioned patch implements an intermediate logging solution according to this spec [0]. And fluentd (EFK) is the target state for future releases, I suppose. It would be great to see it done for Pike though! If it's only possible to leverage EFK for opesntack services using oslo.log, that's okay I believe, let's update the spec. Btw, please take a look and review. It's placed in the tripleo scope but actually it only contains some thoughts on best practives for logging for containers and may be adopted by a broader scope. [0] https://review.openstack.org/#/c/462900/ -- Best regards, Bogdan Dobrelya, Irc #bogdando __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
