1. 16 Jul, 2019 1 commit
  2. 23 Mar, 2019 1 commit
  3. 20 Mar, 2019 5 commits
  4. 19 Feb, 2019 1 commit
    • Pavlo Shchelokovskyy's avatar
      Clarify some config options · 7c5f8362
      Pavlo Shchelokovskyy authored
      current help message to log-config-append is a bit misleading:
      if the extra logging config is using oslo_log's ContextFormatter
      as formatter for some handler, the logging_context_format_string
      option and the like do in fact still apply.
      
      Instead, give the `log-date-format` as example option that does apply
      when log-config-append is enabled and clarify that some options
      are used with ContextFormatter only.
      
      Change-Id: I917cdf8799ac0fb5b49873d5c7bccd957a42f347
      7c5f8362
  5. 20 Dec, 2018 1 commit
  6. 19 Dec, 2018 1 commit
  7. 10 Dec, 2018 1 commit
    • Matt Riedemann's avatar
      Default oslo.policy logging to INFO · 7558bc7c
      Matt Riedemann authored
      As of change https://review.openstack.org/619260/ to oslo.policy
      a lot of information is logged at debug for every policy check,
      which gets to be a lot of information in something like the
      nova-api logs which does a policy check per API request. So this
      change makes the default log level INFO for oslo.policy.
      
      Change-Id: Ie4a114219a69390efd148b705fad05fd8b9a42de
      Related-Bug: #1807747
      7558bc7c
  8. 07 Dec, 2018 2 commits
  9. 05 Dec, 2018 1 commit
  10. 30 Nov, 2018 1 commit
    • Nikita Gerasimov's avatar
      Fix handling of exc_info in OSJournalHandler · a2956d7f
      Nikita Gerasimov authored
      exc_info is exception tuple not intended to be printed. It's using to
      generate output by logging.Formatter().formatException() instead.
      exc_text used to cache this output. So we use handler formatter to get
      string from exc_info and send it as EXCEPTION_INFO. EXCEPTION_TEXT is
      kept for backward compatibility.
      
      Also adds type validation for journal.send fields to unit tests. Known
      types could be gotten from journal.DEFAULT_CONVERTERS. The rest payload
      must be either a string or bytes.
      
      Change-Id: Idc0b9edc61b4ec39dc9df0ea8282cc104e4d83c0
      Closes-Bug: 1802142
      a2956d7f
  11. 29 Nov, 2018 1 commit
    • Ben Nemec's avatar
      Fix up nits in log rotation change · 8db5661b
      Ben Nemec authored
      Just a couple of doc things that became out of date due to some
      code changes during the review process.
      
      Change-Id: I5820f7940d8d32546174da132db5be5a209a2200
      8db5661b
  12. 21 Nov, 2018 1 commit
    • Daniel Vincze's avatar
      Add config options for log rotation · 22e8a347
      Daniel Vincze authored
      On Windows, in-use files cannot be moved or deleted. For this reason,
      we need the service itself to take care of rotating logs.
      
      For convenience reasons, we're exposing the built-in rotating log
      handlers through a set of config options.
      
      More specifically, we're adding the following new config options:
      - log_rotate_interval
      - log_rotate_interval_type
      - max_logfile_count
      - max_logfile_size_mb
      
      Change-Id: I01db4efc08e2cb64db9cbf793f3a159f54859fe7
      Closes-Bug: #1802262
      22e8a347
  13. 13 Nov, 2018 1 commit
  14. 06 Nov, 2018 1 commit
  15. 05 Nov, 2018 1 commit
    • Daniel Vincze's avatar
      Add Windows Event Log handler · 74e8e48a
      Daniel Vincze authored
      The Python built-in logging module already provides a Windows Event
      Log handler. This change ensures that oslo.log exposes it.
      
      Change-Id: I287260b5046c88c433dfa66064da14faf15610e0
      Implements: blueprint windows-event-log
      74e8e48a
  16. 15 Oct, 2018 1 commit
    • ZhongShengping's avatar
      Clean up .gitignore references to personal tools · a9ba6c54
      ZhongShengping authored
      Developers run all sorts of different tools within Git repositories,
      any of which can leave their own special trashfiles all over the
      place. We can't every hope to catalog them all, so better to
      recommend developers simply configure a global core.excludesfile to
      filter the irrelevant files which tend to get created by their
      personal choice of tools.
      
      To this end, remove the long-standing sections for "Mr Developer"
      and "Editors" since their mere existence here sends the signal that
      we welcome (and have time to review) additions for any old tool
      someone ever might happen to try. Also add a comment block
      explaining this, for clarity.
      
      We can, and should of course, continue to list files created by the
      tools recommended by our workflow (test frameworks called from tox,
      documentation and packaging builds, et cetera).
      
      This change is a port of I1b41efac219fca44e2548fc36633724d0ecfc0cb
      from the openstack-dev/oslo-cookiecutter repository.
      
      Change-Id: Ib2c9185265cfe7d2af5afc939f770cf5d5efb6ea
      a9ba6c54
  17. 09 Oct, 2018 1 commit
    • Hervé Beraud's avatar
      Always build universal wheels · 5cd02483
      Hervé Beraud authored
      All of our projects are pure python, so we can build
      universal wheels by default.
      
      Change-Id: I173a1d5b4f204fcda2e92fd751228dbc79009b8c
      5cd02483
  18. 06 Oct, 2018 1 commit
  19. 05 Oct, 2018 1 commit
    • Ben Nemec's avatar
      Add devstack job with JSONFormatter configured · fa045daa
      Ben Nemec authored
      We've run into issues in the past where a service passed something
      to the logger that broke JSONFormatter. To try to catch those sooner,
      add a job that configures the services to use JSONFormatter. This
      should provide a more realistic test of the formatter than we can
      hope to accomplish in unit tests.
      
      Change-Id: Icfb399cfe3dce89dfd5fb5079295a4947828417a
      fa045daa
  20. 03 Sep, 2018 1 commit
  21. 27 Aug, 2018 1 commit
    • Ben Nemec's avatar
      Filter args dict in JSONFormatter · a93c6ef9
      Ben Nemec authored
      In most formatters, any unused keys in the args dict will just be
      discarded.  Because JSONFormatter logged the entire dict in addition
      to the message, some values were included in the output that may
      not have been intended.  This could include sensitive data, so we
      should stop that.
      
      In the interest of maintaining compatibility with any tools that are
      reading the args dict, we leave the dict but filter out any unused
      keys.
      
      Change-Id: Ib64837c1ae93a27bef3d30a776320a373f18dd1c
      Closes-Bug: 1571714
      Closes-Bug: 1787214
      a93c6ef9
  22. 21 Aug, 2018 7 commits
  23. 19 Aug, 2018 6 commits
  24. 12 Aug, 2018 1 commit