[Openstack-operators] looking for feedback on proposals to improve logging

Doug Hellmann doug at doughellmann.com
Fri Apr 28 17:41:47 UTC 2017

Excerpts from Nematollah Bidokhti's message of 2017-04-27 22:30:34 +0000:
> Hi,
> I have been working on the concept of fault management blueprint to increase cloud resiliency. As part of this proposal, info such as logs, KPIs, health checks and so on are critical since we are engaging in deep data analysis and machine learning.
> To ease the data analysis process there must be consistent logs. This comes with having IDs and severity properties.
> Cloud resiliency in general requires fast fault detection, isolation and recovery. In addition, there are applications such as NFV that is sensitive to fast fault detection and recovery. One approach is to have meaningful logs where by parsing the data we can make real time fault management decisions.
> Similar to interrupts, I would like us to have logging hierarchy which can help an automated fault management system to take accurate and appropriate actions. The format of the logs is important since it will ease the ML analysis later in the process.

I'm not sure what you mean by "logging hierarchy". Do you mean the
severity levels that we have (like INFO, WARNING, and ERROR), or
something else?

Are you using the JSON formatter to make the logs easier to parse for
the automated processing you're doing? If so, did you find that complex
to configure? If not, were you aware that was possible and if you were,
what caused you to decide not to use it? Does it not match your needs?


> Thanks,
> Nemat
> -----Original Message-----
> From: Doug Hellmann [mailto:doug at doughellmann.com] 
> Sent: Wednesday, April 26, 2017 7:28 AM
> To: openstack-operators <openstack-operators at lists.openstack.org>
> Subject: [Openstack-operators] looking for feedback on proposals to improve logging
> I am looking for some feedback on two new proposals to add IDs to log messages. Please see the thread on openstack-dev, and comment there or on the specs referenced there.
> http://lists.openstack.org/pipermail/openstack-dev/2017-April/115958.html
> Thanks!
> Doug
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

More information about the OpenStack-operators mailing list