The Movere Console creates two logs: Log.Console.csv and Log.Service.csv. The Console log captures every command issued via the Console while the Service log captures everything pertaining to the scanning process i.e. ping failure, permission denial etc.
Where does Movere store its log files?
Both log files (Log.Console.csv and Log.Service.csv) are stored in the same folder the Movere Console is run from. These logs are NOT sent to UL or its partners automatically. While these logs are extremely helpful in diagnosing problems, the user would need to send these to UL or its partner for a detailed review. In most cases only the service log is required.
What is the format of the log files?
The log files are saved as .csv files, but can opened using any text editor. The log files are cumulative and after several scans the service log file can reach 10MB in size. When this occurs the Movere Console will add an incremental count to the end of the log files name then create a new log file.
What sort of information is in the log files?
Everything the Movere Service does i.e. user account used, launching bot to device, service success, permission issues (both Windows and SQL), event types (e.g. LDAP), upload to the cloud, device being scanned, ping result, saving file locally, etc. is logged.
Are there any logs generated on the remote machines being scanned?
Yes, a small 1KB log file is created. This is used by the Movere Service to see if the endpoint being scanned failed to either return the output file to the device the Movere Console is being run from or directly to the cloud. If both return methods fail then the Movere Service pulls the output file back.