[Bro-Dev] [JIRA] (BIT-1490) Need ability to expire logs with more granularity than #days.

Daniel Thayer (JIRA) jira at bro-tracker.atlassian.net
Mon Oct 12 15:59:00 PDT 2015

    [ https://bro-tracker.atlassian.net/browse/BIT-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22500#comment-22500 ] 

Daniel Thayer commented on BIT-1490:

Branch "topic/dnthayer/ticket1490" in the broctl repo changes the
LogExpireInterval option to accept a value that is a time interval,
such as "30min", "12hr", or "7day".  A value of 0 still means do
not expire logs.  An integer without a time unit still means "days"
(so that users can still use their old config files).

> Need ability to expire logs with more granularity than #days.
> -------------------------------------------------------------
>                 Key: BIT-1490
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-1490
>             Project: Bro Issue Tracker
>          Issue Type: Improvement
>          Components: BroControl
>    Affects Versions: git/master
>            Reporter: Seth Hall
>            Assignee: Daniel Thayer
>            Priority: Low
> There are some users that would like or need to have BroControl maintain their collected logs with tighter granularity than how many days old the logs are.
> Right now the find command that determines which files to delete uses `-mtime` which is `x*24hr`.  We would need to use the `-mmin` argument otherwise, but I suspect this would introduce the need to do some parsing of of the value given so that people could specify things like `10hr` or `5days`.

This message was sent by Atlassian JIRA

More information about the bro-dev mailing list