Logging: Expire by configuration #30

Closed
opened 2014-09-18 17:03:20 +00:00 by thorsten · 0 comments
thorsten commented 2014-09-18 17:03:20 +00:00 (Migrated from devops.tsommer.org)

TODOs

  • Read the documentation about ExpireAfter on mgo.Index of mgo!
  • After the index is present, how to disable it afterwards? Does EnsureIndex() also updates the entry?
  • Test the expire function
  • Test the disable of the expire function

Idea

  • Let the administrator choose if the logging entries should automatically expire (one config. value)
  • Let the administrator configure the expire time [days](another config. value)
  • Side effect: A change of this value consider no old loggings, just the new ones.
### TODOs - [x] Read the documentation about ExpireAfter on mgo.Index of mgo! - [x] After the index is present, how to disable it afterwards? Does EnsureIndex() also updates the entry? - [ ] Test the expire function - [ ] Test the disable of the expire function ### Idea - Let the administrator choose if the logging entries should automatically expire (one config. value) - Let the administrator configure the expire time [days](another config. value) - Side effect: A change of this value consider no old loggings, just the new ones.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Go/Ocean#30
No description provided.