<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><p class="airmail_on">On 11 March 2016 at 11:34:32, Igor Kalnitsky (<a href="mailto:ikalnitsky@mirantis.com">ikalnitsky@mirantis.com</a>) wrote:</p> <div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div></div><div>Hey Roman,<br><br>Thank you for bringing this up. +1 from my side, especially taking<br>into account the patch where we tried to solve logrotated logs problem<br>[1]. It's complex and unsupportable, as well as already existed<br>logview code in Nailgun.<br><br>Patrick, Simon,<br><br>Does LMA plugin support logs from master node? Or it's designed to<br>watch environment's logs?</div></div></span></blockquote></div><p>No it’s not designed specifically for environment logs. Can be adapted to any log format.</p><p>Would just need to write a parser like you would with logstach when logs are not standard.</p><p>Patrick</p><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span><div><div><br><br>Thanks,<br>Igor<br><br><br>[1]: https://review.openstack.org/#/c/243240/<br><br>On Fri, Mar 11, 2016 at 11:53 AM, Patrick Petit <ppetit@mirantis.com> wrote:<br>> Fuelers,<br>><br>> As Simon said, we already have a log centralisation solution for MOS<br>> delivered as a Fuel plugins known as StackLight / LMA toolset. And so<br>> objectively, there is no need to have log management in Nailgun anymore. To<br>> go one step further we suggested several times to have a StackLight agent<br>> installed on the Fuel master node to also collect and centralise those logs.<br>> There is a little bit of a chicken and egg problem to resolve but I think it<br>> is worth a try to have that nailed down in the roadmap for Fuel 10.<br>> Cheers<br>> - Patrick<br>><br>><br>> On 11 March 2016 at 10:07:28, Simon Pasquier (spasquier@mirantis.com) wrote:<br>><br>> Hello Roman,<br>><br>> On Fri, Mar 11, 2016 at 9:57 AM, Roman Prykhodchenko <me@romcheg.me> wrote:<br>>><br>>> Fuelers,<br>>><br>>> I remember we’ve discussing this topic in our couloirs before but I’d like<br>>> to bring that discussion to a more official format.<br>>><br>>> Let me state a few reasons to do this:<br>>><br>>> - Log management code in Nailgun is overcomplicated<br>>> - Working with logs on big scale deployments is barely possible given the<br>>> current representation<br>>> - Due to overcomplexity and ineffectiveness of the code we always get<br>>> recurring bugs like [1]. That eats tons of time to resolve.<br>>> - There are much better specialized tools, say Logstash [2], that can deal<br>>> with logs much more effectively.<br>>><br>>><br>>> There may be more reasons bus I think even the already mentioned ones are<br>>> enough to think about the following proposal:<br>>><br>>> - Remove Logs tab from Fuel Web UI<br>>> - Remove logs support from Nailgun<br>>> - Create mechanism that allows to configure different log management<br>>> software, say Logstash, Loggly, etc<br>>><br>>> - Choose a default software to install and provide a plugin for it from<br>>> the box<br>><br>><br>> This is what the LMA/StackLight plugins [1][2] are meant for. No need to<br>> develop anything new.<br>><br>> And I'm +1 with the removal of log management from Fuel. As you said, it<br>> can't scale...<br>><br>> [1] http://fuel-plugin-lma-collector.readthedocs.org/en/latest/<br>> [2] http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/<br>><br>><br>>><br>>><br>>><br>>> References<br>>> 1. https://bugs.launchpad.net/fuel/+bug/1553170<br>>> 2. https://www.elastic.co/products/logstash<br>>><br>>><br>>> - romcheg<br>>><br>>> __________________________________________________________________________<br>>> OpenStack Development Mailing List (not for usage questions)<br>>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>>><br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>><br>><br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br>><br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div></div></span></blockquote></div></body></html>