Migrating a legacy log into new SoftActivity Webapp
Prior to version 11.0 of Activity Monitor the logs had been sorted in a database consisting of a single file with .salog extension. Screenshots are stored in SCR folder located next to the .salog file.
Starting with Activity Monitor 11.0 it uses new enterprise class PostgreSQL database server for storing logs. Customers can keep .salog log files and view them in legacy Log Viewer desktop applications.
Although there is an option to migrate your legacy .salog log file into the new PostgreSQL database, so that they can be viewed in SoftActivity webapp. Follow these steps to migrate the logs:
- Setup your webapp and the database settings properly in Activity Monitor Options and verify that new logs appear in your web console.
- Login to the web console, go to Application Settings and set a desired data retention interval, such as a few months. Otherwise it will store logs indefinitely and fill the server’s hard drive
- Stop SalogSrv service temporarily, to pause downloading of new logs while the import runs
- Open Command Prompt As Administrator on the machine with Activity Monitor Server installed
- Run this command to navigate it to Activity Monitor folder :
cd "%ProgramFiles(x86)%\SoftActivity\Activity Monitor"
- Run this command to start data migration from .salog file to PostgreSQL database:
pgexport.exe --cfg=C:\ProgramData\Salog\sa_webapp.cfg --salogfile="C:\Users\user\Documents\Activity Monitor Logs\log_db.salog" --scrsource="C:\Users\user\Documents\Activity Monitor Logs\SCR" --scrdest="C:\ProgramData\Salog\data\scr-web" --log=all
cfg – location of the webapp config file. Do not change this
salogfile – legacy database .salog file that you want to migrate to the webapp. Usuaully, the legacy log file can be found in Documents\Activity Monitor\Logs
scrsource – SCR folder corresponding to the above legacy database file. Usually it’s located next to the .salog file. All screenshots will be moved to the new folder specified in /scrdest
scrdest – Central Storage folder for screenshots, used in the webapp. You can see it in Options – Database tab
- Wait a few minutes until pgexport.exe succeeds copying all data. It may take a long time for a large volume of screenshots, especially when migrating screenshots to a different drive, or a network drive.
Note: On large databases it may take several hours for import to complete
- In case the command return any errors, those issues need to be addressed. Then re-run the command
- Start SalogSrv service in order to continue downloading of new logs from monitored computers.
- you need to have access under your user account to the files and folders specified in the above command in salogfile, scrsource and scrdest parameters
- in case the legacy database is encrypted (asks for a password when opened in legacy Log Viewer), you will need provide your previous password in salogpass command line parameter:
- pgexport.exe was not included in some older builds of Activity Monitor 11. To get this command line migration utility upgrade to the latest version or contact SoftActivity