Go/Ocean
1
0 Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Logging: Expire by configuration #30

New Issue
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)
Copy link
Copy source

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 Branch/Tag Specified
Labels
Clear labels
Comp::Backend
Comp::Database
Comp::ICCC
Comp::Logging
Comp::Sessions
Comp::System
Comp::Users
Ready2Test
bug
change
check
enhancement
note
outdated
Outdated since Ocean is no longer maintained
 question
security
todo
wontfix
No labels Comp::Logging enhancement todo
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
tsommer
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Go/Ocean#30