When starting up the BES Console the time from when I supply my username and password to the time I can work within the console continues to increase, with it now taking over a minute. I see these two messages as the progress bars creep across the screen :
“Importing action site store ~1300 records…”
“Importing actions ~28,000 records”
When closing the program, I incur another wait with the reciprocal messages being shown :
“Writing out ~1,300 site action records…”
“Writing out ~28,000 action records…”
Is there anything I can do to clean these up? The other console users are rather displeased with the wait times.
The console loads up actions and their results to give you all the info you see in the action tab. If you accumulate lots of actions with lots of action results, it takes longer to load… You can prune this down by deleting actions you don’t need any more and the console won’t bother to load them anymore…
You might also consider contacting our professional services team for a remote “optimization service” and they will review your system and let you know if they think there are improvements you can make… See here (and the datasheet): http://support.bigfix.com/services/
I’ve read that as an actional item within the BigFix Health Deployment dashboard and it makes reference to the logs still being in the database for the sake of auditing.
How can I look up the logs of actions I have deleted out of BigFix?
When you delete an action from the BES Console the data is preserved in the database but marked as being deleted so the console won’t load the data anymore.
If you needed to review actions you could either:
Undelete the action so you can see it in the BES Console using the stored procedure undelete_action
Run SQL queries to get the data you are interested in
Also, you should try the different caching options in the preferences pane of your console. I’ve found, particularly when running in VMs, that the ‘all ways load from database’ option can be the fastest. It’s probably worth it to try all three options.