| Include Page | ||||
|---|---|---|---|---|
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
This page presents suggestions for ongoing Grouper administration tasks, including:
...
Pruning Logs and Registry
change log
daemon loglogs
user audit logs
point in time logs
registry
...
By default, change log entries are retained for 14 days in grouper_change_log_entry. This is configurable in grouper-loader.properties. Note that this option doesn't exist before Grouper 2.0.
| Code Block |
|---|
# number of days to retain db rows in grouper_change_log_entry. -1 is forever. default is 14
loader.retain.db.change_log_entry.days=14
|
...
By default, these logs are retained for 7 days. This is also configurable in grouper-loader.properties.
| Code Block |
|---|
# number of days to retain db logs in table grouperloader_log. -1 is forever. default is 7
loader.retain.db.logs.days=7
|
...
Here's an example to delete rows based on time. Note that created_on is milliseconds from epoch.
| Code Block |
|---|
delete from grouper_audit_entry where created_on < '1318599550575'
|
...
- Set up Nagios to check the Grouper Diagnostics web service status page to be sure the daemons are running and the DB is up etc
...
- Periodically check a service that uses XMPP to make sure the messaging is still working
- Check the daily Grouper report to get a summary of the total state of your Grouper installation
...
- For email notification of items such as membership changes, disable date changes, or permission changes, use rules and follow the examples for use cases on email notification.