Boris Pavlovic af1c8b7652 Improve Rally Logging (part 2)
- Remove translations

  Nobody is using translations for Rally and I don't think that
  anybody is going to use it. Target auditory for Rally are
  developers/operators which usually know well english.
  For me this looks like waste of resources, performance
  degradation (cause we are calling _()), complexity
  (+1 thing that you need to know)

- Pass to log already formatted strings

  It's very bad because in case of wrong formatting, it
  doesn't fail instead just writes errors to the logs,
  as well information about trace is lost, so it's super
  hard to fix it

  Log wrapper doesn't allow to use LOG anymore for
  formatting strings

  All places are fixed

- Improve logging of exceptions

LOG.exception() already logs exception, which means it's bad idea to
pass str(e) to it. Instead we should provide clear description of what
happend. Improved few places to write warnings or exceptions in case
of different level of logs. In few places just use LOG.exception

- Part of log messages were improved and simplified

Depends-On: If23d874e8b73de12ba2b8c4e028a55543af6381b
Change-Id: Ibc1e1f4f554649d14b8fe4801557b83922ecefe3
2017-10-05 22:57:39 +00:00
..
2017-05-27 15:09:42 +02:00
2017-10-05 22:57:39 +00:00
2017-02-07 15:28:53 +02:00
2017-01-23 10:16:49 +00:00
2017-04-20 10:06:57 +05:30
2017-08-03 18:39:10 +00:00
2014-06-05 17:45:51 +03:00