In scenarios with 10k or more associated devices it happens a fixstates lasts up to serveral hours. This feature gives the possibility to enable a more verbose fixstates to better follow its evolution and check its current status.
- datetime is written next to main events
- keeps the count of currently analyzed devices
- moves to INFO level a few DEBUG level logs usefull to be monitored while executing fixstates in production enviroments, without having to give an extra load to the system by passing all log to DEBUG level.
- It can be enabled by defining an optional LOGFIXSTATES value set to true in the configuration file
It also fixes an inaccuracy in "Checking for unreferenced (obsolete) state files: Processed: X - Deleted: Y" , as FixStatesUserToStatesLinking function was returning the count of processed and deleted state files of the last processed device only and not of the sum of all processed devices.