#48 ✓resolved
labman

Prune activity log

Reported by labman | October 7th, 2008 @ 09:58 AM | in 5.0.3 (closed)

The activity log can grow very quickly and it would be helpful to be able to prune it either manually or through an automatic setting without having to manually manipulate the database tables.

Comments and changes to this ticket

  • lux

    lux January 4th, 2009 @ 02:57 PM

    Also scheduler log file and versioning tables. For the latter, it would need a setting that says:

    Versions to keep? All, 1, 2, 5, 10, 20

    Or something to that effect. These would best be implemented through the scheduler I would think.

  • Charles Brunet

    Charles Brunet July 29th, 2009 @ 04:20 PM

    • Assigned user changed from “lux” to “Charles Brunet”
    • State changed from “new” to “open”
    • Tag changed from activity, feature, log to activity, feature, history, log, scheduler, version

    Done for activity log and for versionning history.

    Scheduler log is still to do.

  • Charles Brunet

    Charles Brunet August 4th, 2009 @ 04:22 PM

    • State changed from “open” to “resolved”

    implemented logrotate scheduler task to rotate scheduler logs.

  • Charles Brunet

    Charles Brunet August 7th, 2009 @ 09:41 AM

    • Milestone set to 5.0.3

    [milestone:id#47011 bulk edit command]

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

The Sitellite web content management system.

People watching this ticket

Pages