As Matt discussed, there is a push to better identify debug messages (and the packages) that are important to operators. In a subsequent session it was discussed about creating etherpads to make it easier to identify DEBUG messages that are in use and important for analysis, and for ease of reference any DEBUG messages that are regularly discarded, e.g. in any log analysis patterns. The two etherpads have been setup to help better identify and classify DEBUG log messages. https://etherpad.openstack.org/p/ops-debug-messages-in-use https://etherpad.openstack.org/p/ops-debug-messages-discarded Regards Ronald On Mon, Apr 25, 2016 at 11:10 PM, Matt Jarvis <matt.jarvis at datacentred.co.uk > wrote: > One of the discussion points which came up in the Logging session at the > Ops Summit today was that a lot of operators are running with debug logging > enabled. There was a request from development to understand more about why > that might be needed, ie. under what circumstances are operators not > getting enough logging information without debug logging. If you are > running one of the core projects with debug logging enabled, are there > specific scenarios under which that has been needed to solve operational > issues ? It would be really helpful if we could get some wider input from > the ops community around this. > > DataCentred Limited registered in England and Wales no. 05611763 > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160503/b564dc77/attachment.html>