No rotating file option

Bug #1802262 reported by Lucian Petrut
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.log
Fix Released
Wishlist
Daniel Vincze

Bug Description

On Windows, in-use files cannot be renamed or deleted. For this reason, we need the service itself to take care of rotating log files.

The built-in logging module already provides a couple of rotating file handlers. For convenience reasons, it would be nice if oslo.log could expose them through a set of config options.

Changed in oslo.log:
status: New → Incomplete
status: Incomplete → New
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.log (master)

Fix proposed to branch: master
Review: https://review.openstack.org/616464

Changed in oslo.log:
assignee: nobody → Daniel Vincze (dvincze)
status: New → In Progress
Ben Nemec (bnemec)
Changed in oslo.log:
importance: Undecided → Wishlist
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.log (master)

Reviewed: https://review.openstack.org/616464
Committed: https://git.openstack.org/cgit/openstack/oslo.log/commit/?id=22e8a347c8ba914cefa26df42dde632937259a79
Submitter: Zuul
Branch: master

commit 22e8a347c8ba914cefa26df42dde632937259a79
Author: Daniel Vincze <email address hidden>
Date: Wed Nov 7 14:49:42 2018 +0200

    Add config options for log rotation

    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

Changed in oslo.log:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.log 3.42.0

This issue was fixed in the openstack/oslo.log 3.42.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.