What is the stance on keeping expired actions around in the console? The previous BigFix admin said that he was told by IBM to remove actions after they expired to keep the system running smooth. If that’s the case, how do you keep tabs on things that have happened in the BigFix environment? If that’s not the case, is there a tipping point where keeping X number of expired actions would have an adverse effect on the BigFix system?
- How many console operators do you have?
- What is the maximum number of simultaneous console operators you normally have?
Stopped & Expired actions primarily affect console performance. If your console performs well, then you don’t need to clear them out all of the time.
It is probably a good idea to clear them out if they are older than a certain time period. The more console operators you have, the more aggressively you should clear them out.
Deleted actions no longer show up in the console, but their information is still available in the database. Also, I believe even deleted actions have some impact on console performance until they are completely removed using the Audit Trail Cleaner.
OK, that clears things up a bit.
If the actions are still in the database after removing from the console, is there an easy way to query for past actions that have been deleted? @jgstew
You have to use the Database API views and SQL queries.