Yeah that's true. We did all of openstack systems but we didn't implement infra around yet. I'd guess most of services can log either to stdout or file, and both sources should be accessible by heka. Also, I'd be surprised if heka wouldn't have syslog driver? That should be one of first:) Maybe worth writing one? I wanted an excuse to write some golang;)
Regards, Michal On 15 January 2016 at 06:42, Eric LEMOINE <[email protected]> wrote: > On Fri, Jan 15, 2016 at 11:57 AM, Michal Rostecki > <[email protected]> wrote: >> On 01/15/2016 11:14 AM, Simon Pasquier wrote: >>> >>> My 2 cents on RabbitMQ logging... >>> >>> On Fri, Jan 15, 2016 at 8:39 AM, Michal Rostecki <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> I'd suggest to check the similar options in RabbitMQ and other >>> non-OpenStack components. >>> >>> >>> AFAICT RabbitMQ can't log to Syslog anyway. But you have option to make >>> RabbitMQ log to stdout [1]. >>> BR, >>> Simon. >>> [1] http://www.superpumpup.com/docker-rabbitmq-stdout >>> >> >> That's OK for Heka/Mesos/k8s approach. >> >> Just for the curiosity, >> @inc0: so we don't receive any logs from RabbitMQ in the current rsyslog >> approach? > > > /var/lib/docker/volumes/rsyslog/_data is where logs are stored, and > you'll see that there is no file for RabbitMQ. This is related to > RabbitMQ not logging to syslog. So our impression is that Kolla > doesn't at all collect RabbitMQ logs today. I guess this should be > fixed. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
