Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-13 Thread Kwasniewska, Alicja
, January 13, 2016 10:55 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Introduction of Heka in Kolla Hi Alicja Thank you for your comments. Answers and comments below. On Tue, Jan 12, 2016 at 1:19 PM, Kwasniewska, Alicja

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-13 Thread Eric LEMOINE
Hi Alicja Thank you for your comments. Answers and comments below. On Tue, Jan 12, 2016 at 1:19 PM, Kwasniewska, Alicja wrote: > Unfortunately I do not have any experience in working or testing Heka, so > it’s hard for me to compare its performance vs Logstash

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-13 Thread Patrick Petit
[mailto:sam...@yaple.net] Sent: Monday, January 11, 2016 11:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Introduction of Heka in Kolla   Here is why I am on board with this. As we have discovered, the logging with the syslog plugin leaves

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-13 Thread Eric LEMOINE
On Tue, Jan 12, 2016 at 5:36 PM, Michał Jastrzębski wrote: > So tracebacks sort of works, they're there just ugly. That's why I'm > also happy if we change rsyslog to heka. > > Eric, I hope I wont ask too much, but could you please prepare PoC of > kolla+heka, for what I care

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-13 Thread Eric LEMOINE
On Tue, Jan 12, 2016 at 8:26 PM, Steven Dake (stdake) wrote: > Eric, > > Thanks for using the mailing list for this discussion. I like to see more > mailing list conversations on big changes related to kolla, which this one > is :) > Responses inline. > > Please put document #3

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-12 Thread Simon Pasquier
eka-monitorama-2015-06/#/41 > > > > * Alicja Kwaśniewska* > > > > *From:* Sam Yaple [mailto:sam...@yaple.net] > *Sent:* Monday, January 11, 2016 11:37 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [kolla]

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-12 Thread Clark Boylan
On Tue, Jan 12, 2016, at 04:19 AM, Kwasniewska, Alicja wrote: > Unfortunately I do not have any experience in working or testing Heka, so > it’s hard for me to compare its performance vs Logstash performance. > However I’ve read that Heka possess a lot advantages over Logstash in > this scope. >

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-12 Thread Steven Dake (stdake)
Eric, Thanks for using the mailing list for this discussion. I like to see more mailing list conversations on big changes related to kolla, which this one is :) Responses inline. Please put document #3 (the design document) in gerrit rather than google docs in the main kolla repo as a spec

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-12 Thread Michał Jastrzębski
So tracebacks sort of works, they're there just ugly. That's why I'm also happy if we change rsyslog to heka. Eric, I hope I wont ask too much, but could you please prepare PoC of kolla+heka, for what I care heka can log to local log file same as rsyslog for now. Would that be big problem? On 11

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Sam Yaple
Here is why I am on board with this. As we have discovered, the logging with the syslog plugin leaves alot to be desired. It (to my understanding) still can't save tracebacks/stacktraces to the log files for whatever reason. stdout/stderr however works perfectly fine. That said the Docker log

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Eric LEMOINE
Le 11 janv. 2016 18:45, "Michał Jastrzębski" a écrit : > > On 11 January 2016 at 10:55, Eric LEMOINE wrote: > > Currently the services running in containers send their logs to > > rsyslog. And rsyslog stores the logs in local files, located in the > >

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Eric LEMOINE
On Mon, Jan 11, 2016 at 5:01 PM, Michał Jastrzębski wrote: > On 11 January 2016 at 09:16, Eric LEMOINE wrote: >> * Logstash was designed for logs processing. Heka is a "unified data >> processing" software, designed to process streams of any type of

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Michał Jastrzębski
On 11 January 2016 at 09:16, Eric LEMOINE wrote: > Hi > > As discussed on IRC the other day [1] we want to propose a distributed > logs processing architecture based on Heka [2], built on Alicja > Kwasniewska's ELK work with > .

[openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Eric LEMOINE
Hi As discussed on IRC the other day [1] we want to propose a distributed logs processing architecture based on Heka [2], built on Alicja Kwasniewska's ELK work with . Please take a look at the design document I've started working on [3]. The document

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Sam Yaple
I like the idea of using Heka. You and I have discussed this on IRC before. So my vote for this is +1. I can't think of any downside. I would like to hear Alicja Kwasniewska's view on this as she has done the majority of work with Logstash up until this point. Sam Yaple On Mon, Jan 11, 2016 at

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

2016-01-11 Thread Michał Jastrzębski
On 11 January 2016 at 10:55, Eric LEMOINE wrote: > On Mon, Jan 11, 2016 at 5:01 PM, Michał Jastrzębski wrote: >> On 11 January 2016 at 09:16, Eric LEMOINE wrote: > >>> * Logstash was designed for logs processing. Heka is a