Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Fri, Jan 15, 2016 at 2:40 PM, Michał Jastrzębski wrote: > 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

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

My 2 cents on RabbitMQ logging... On Fri, Jan 15, 2016 at 8:39 AM, Michal Rostecki 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

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

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 > wrote: I'd suggest to check the similar options in RabbitMQ and other non-OpenStack components.

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Fri, Jan 15, 2016 at 11:57 AM, Michal Rostecki 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 > > wrote: >> >>

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

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

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On 15 Jan 2016 at 14:43:39, Michał Jastrzębski (inc...@gmail.com) wrote: 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

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

> > In case of MariaDB I see that you can > > - do --skip-syslog, then all things go to "error log" > - set "error log" path by --log-error > > So maybe setting stdout/stderr may work here? > > I'd suggest to check the similar options in RabbitMQ and other non-OpenStack > components. > > I may

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Wed, Jan 13, 2016 at 1:15 PM, Steven Dake (stdake) wrote: > Hey folks, > > I'd like to have a mailing list discussion about logistics of the ELKSTACK > solution that Alicja has sorted out vs the Heka implementation that Eric is > proposing. > > My take on that is Eric wants

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On 01/14/2016 03:56 PM, Michał Jastrzębski wrote: On 14 January 2016 at 04:46, Eric LEMOINE wrote: On Wed, Jan 13, 2016 at 1:15 PM, Steven Dake (stdake) wrote: Hey folks, I'd like to have a mailing list discussion about logistics of the ELKSTACK

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On 14 January 2016 at 04:46, Eric LEMOINE wrote: > On Wed, Jan 13, 2016 at 1:15 PM, Steven Dake (stdake) > wrote: >> Hey folks, >> >> I'd like to have a mailing list discussion about logistics of the ELKSTACK >> solution that Alicja has sorted out vs the

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

So is it decided that we want Heka instead of ELK in Kolla and that it is just a matter of time, then ? Clark Boyle put forward some very good points [1] which seem to have gone sadly mostly ignored. What are we trying to address by replacing ELK ? Performance ? Clark's numbers are far from

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

5:55 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] Heka v ELK stack logistics So is it decided that we want Heka instead of ELK in Kol