You can set the age limits at which activity and unused objects are deleted from the Repository. For each grooming option, specify an age from 1 to 365 days.
To set your grooming options, follow these steps:
- Start the IDERA Newsfeed Platform Manager console.
- Click the Repository tab.
- Under Grooming Options, select the application age limits for activity and objects. You can specify an age from 1 to 365 days.
- Click Save.
The setup program installs a single grooming job that is scheduled to run on the Repository at midnight each day. This job calculates the age of all Newsfeed activity and objects stored in the Repository, and detects whether any instances have been removed from SQLDM. When the job finds stale active or disabled objects that are older than the specified age limit, it deletes the corresponding data, including all associated posts, status updates, comments, and bookmarks.
What gets groomed?
By default, the IDERA Newsfeed Platform grooms all unused objects and stale activity. You can change many of the age limits used to determine when to groom a specific object or activity.
- Applications that have been disabled for more than 45 days.
- Notifications older than 7 days.
- Newsfeed user accounts that have been disabled for more than 45 days.
- Servers that have not been monitored by the SQLDM application for more than 45 days.
- Stories older than 30 days.
If an older story has had recent activity, such as a new comment, within the specified age limit, the IDERA Newsfeed Platform does not groom the story.
How often should I groom data?
How often you groom data — that is, how old you allow stories to get before deleting them from the SQLDM Mobile Repository — depends on these factors:
| Factor | Why | How |
|---|---|---|
The number of status updates that have been published by the SQLDM application | Based on this publication rate, you can determine how quickly the Repository database is growing to accommodate these stories, and how soon you will need to delete older stories to make room for future stories. | Use the Applications tab of the IDERA Newsfeed Platform Manager console to check the publication rate for your SQLDM application. |
The amount of activity the average story gets | Because important issues typically receive the most attention, and get the most activity, you can gauge how long a story continues before it is considered "stale" by your team. | Use the activity timeline to track bursts of activity and identify how many stories are responsible for these peaks. |
Life-cycle of the average issue | The age limit at which you groom a story should be set to 2-5 business days from the point at which an issue is typically resolved, allowing ample time for your team to see the issue, respond to it, update the story, and note the solution. | Follow a few typical stories to see how they evolve and review your team's current issue resolution workflows. |
To keep an ongoing record of how key critical issues were solved, encourage your team to bookmark the corresponding stories, ensuring they will always have access to that information.