Re: [Openstack-operators] [log] LOG.exception should contain an exception message or not?

2016-01-15 Thread Saverio Proto
I think the stacktrace is usefull when debugging, even as an operator. Instead of changing the logs to satisfy the tools, it is the tools that should be enable to parse the logs correctly. Saverio 2016-01-05 14:08 GMT+01:00 Akihiro Motoki : > Hi, > > # cross-posting to -dev

Re: [Openstack-operators] [log] LOG.exception should contain an exception message or not?

2016-01-05 Thread Joshua Harlow
Perhaps the recommendation should be to not use line-oriented tools (and formatters) for logs? At least at yahoo we use the json formatter provided by oslo.log and then use the functionality of splunk to handle json records (which afaik is built-in). Likely other tools can also handle json

[Openstack-operators] [log] LOG.exception should contain an exception message or not?

2016-01-05 Thread Akihiro Motoki
Hi, # cross-posting to -dev and -operators ML In the current most OpenStack implementation, when we use LOG.exception, we don't pass an exception message to LOG.exception: LOG.exception(_LE("Error while processing VIF ports")) IIUC it is because the exception message will be logged at the