fuel-dev team mailing list archive

[Bogdan Dobrelya <bdobrelia@xxxxxxxxxxxx>]

On 01/29/2014 10:36 PM, Sanchez, Cristian A wrote:
> Hi Bogdan,
> My name is Cristian Sanchez, I work for Intel in a team 
> contributing to Openstack. Specifically, our team has been
> trying to contribute around centralized logging mechanisms.
> This blueprint:
> https://blueprints.launchpad.net/fuel/+spec/logstash-elastic
> search-kibana-for-logs looks related to our contributions 
> intentions. Now I see that the blueprint is Deferred and
> waiting for Kibana UI v3. Is that the case?
> Please let us know if you need some help on this. 
> We’d gladly contribute to the remaining work.
> 
> Cheers,
> 
> Cristian
> 

+ fuel-dev list
Hi Sanchez.
Currently we are experiencing some stability issues with Logstash and
Elasticsearch backend in our PoC implementation. Logstash-agent service
sporadically crashes with
  :message=>"thread watchdog timeout",

:backtrace=>["file:/usr/share/java/logstash.jar!/logstash/filterworker.rb:46',
  :level => :fatal'
error which looks being caused either by ruby regex parsing engine or by
Elasticsearch indexing failures or by JRE issues as well... I have no
clear vision of the source/fix of this stability issue yet.

There are also many indexing warnings, e.g.
  :message=>"Failed to index an event, will retry",
  :exception=>org.elasticsearch.transport.RemoteTransportException:
[Choice][inet[/<ip>:9300]][index]
but I can see these messages in UI as successfully parsed anyway.

Had you guys also experienced the same (or similar) issues?

The one more issue is Kibana 2 usability related - it has no ability to
save searching patterns as a presets. Kibana 3 has it as well as other
major UI enhancements. But looks like it is distributed as
zip-balls/github clones only. We need it be packaged as RPM somehow.

-- 
Best regards,
Bogdan Dobrelya,
Researcher TechLead, Mirantis, Inc.
+38 (066) 051 07 53
Skype bogdando_at_yahoo.com
Irc #bogdando
38, Lenina ave.
Kharkov, Ukraine
www.mirantis.com
www.mirantis.ru
bdobrelia@xxxxxxxxxxxx