Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2015-02-02 Thread Simon Pasquier
Hello, (resurrecting this old thread because I think I found the root cause) The problem affects all OpenStack environments using Syslog, not only Fuel-based installations: when use_syslog is true, the logging_context_format_string and logging_default_format_string parameters aren't taken into acc

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-16 Thread Dmitry Pyzhov
Guys, thank you for your feedback. As a quick and dirty solution we continue to hide extra information from UI. It will not break existing user experience. Roman, there were attempts to get rid of our current web logs page and use Logstash. As usual, it's all about time and resources. It is our ba

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-15 Thread Roman Prykhodchenko
Hi folks! In most productions environments I’ve seen bare logs as they are shown now in Fuel web UI were pretty useless. If someone has an infrastructure that consists of more that 5 servers and 5 services running on them they are most likely to use logstash, loggly or any other log management

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-15 Thread Aleksey Kasatkin
+1 to show "as is". We don't get benefits from parsing now (like filtering by value of particular parameter, date/time intervals). It only adds complexity. Aleksey Kasatkin On Mon, Dec 15, 2014 at 1:40 PM, Tomasz Napierala wrote: > > Also +1 here. > In huge envs we already have problems with

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-15 Thread Tomasz Napierala
Also +1 here. In huge envs we already have problems with parsing performance. In long long term we need to think about other log management solution > On 12 Dec 2014, at 23:17, Igor Kalnitsky wrote: > > +1 to stop parsing logs on UI and show them "as is". I think it's more > than enough for al

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-12 Thread Igor Kalnitsky
+1 to stop parsing logs on UI and show them "as is". I think it's more than enough for all users. On Fri, Dec 12, 2014 at 8:35 PM, Dmitry Pyzhov wrote: > We have a high priority bug in 6.0: > https://bugs.launchpad.net/fuel/+bug/1401852. Here is the story. > > Our openstack services use to send l

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-12 Thread Jay Pipes
On 12/12/2014 01:35 PM, Dmitry Pyzhov wrote: We have a high priority bug in 6.0: https://bugs.launchpad.net/fuel/+bug/1401852. Here is the story. Our openstack services use to send logs in strange format with extra copy of timestamp and loglevel: ==> ./neutron-metadata-agent.log <== 2014-12-12T1

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-12 Thread Rochelle Grober
./neutron-metadata-agent.log, file it as a bug so that the code can be refactored as either a bug fix or a “while you’re in there” step. --rocky From: Dmitry Pyzhov [mailto:dpyz...@mirantis.com] Sent: Friday, December 12, 2014 10:35 AM To: OpenStack Dev Subject: [openstack-dev] [Fuel] Logs format on

[openstack-dev] [Fuel] Logs format on UI (High/6.0)

2014-12-12 Thread Dmitry Pyzhov
We have a high priority bug in 6.0: https://bugs.launchpad.net/fuel/+bug/1401852. Here is the story. Our openstack services use to send logs in strange format with extra copy of timestamp and loglevel: ==> ./neutron-metadata-agent.log <== 2014-12-12T11:00:30.098105+00:00 info: 2014-12-12 11:00:30.