Your LaunchBoost dashboard provides you with some real-time patch logs for your patch system.
These are not in-depth debug logs, they are simply just ‘hits’ to the LaunchBoost service and your account to keep you informed of what is going on.
User IDs
Every single one of your users who runs your patch system will have their own unique User ID. This User ID is unique to them and cannot be replicated. This is useful information as you can see what messages were posted by which individual user.
If a user is experiencing difficulties with your patch system, you should inform them to run the patch system again. If the error occurs again, they will be presented with the user debug log and it will contain at the top, their User ID. They can give you this User ID so you can search this table to see what messages they sent.
You can also ask them to send you the debug log so you can check over what is causing the error. You can search these docs for ‘User Debug Log’.
Response Types
There are four types of response types. They are ‘info’ – ‘error’ – ‘success’ – ‘connect’.
info – This is information a client has sent to the server with regards to their patching. These are not error messages. They just contain useful information such as MB:<value> and this represents the client downloaded X amount of MBs during that patch session.
error – This is the error response type. When a client has an error with their patching system, an error message is sent to your patch logs here on the server. If you see a lot of these, there’s a critical problem with your patch system and the setup.
connect – This is the connect response type. When a client has run the patch system and successfully connected to your LaunchBoost account and retrieved the patch settings. This just indicates a successful connection.
success – This is the success response type. This will be sent to the server when a user successfully completes the entire patch process and has updated successfully.
How to Debug User Errors
When the user experiences an error with your patch system, you should instruct them to try the patch system for a second time. The patch system will realise that the first time was unsuccessful and will start debug logging locally on the user’s computer. When this happens and the patch system crashes or errors out again, the user will be presented with the debug log. It will automatically open on their PC. At the top, they have a unique User ID. You can use that User ID to search your patch log table. You may need to refresh the Patch Logs page.
The table will then show all the messages relating to this user id so you can analyse a few things.
If you cannot fathom what the issue could be, then you need to ask them to send you that debug log file by saving it to their computer somewhere and emailing it to you or sending it to you.
Once you have the user debug log, you should then proceed to follow the User Debug Log guide on this documentation website.
Searching for Information
The search box above the patch log table is very versatile. You can type in any kind of text and it will filter down the rows corresponding or containing that text. Don’t shy away from using this search box.
In order to clear the search, you can either refresh the page or click the X button inside the search box to clear the filter.
You can also SORT the information displayed in the patch log table by clicking on the relevant header column.
Log Time Limits
Logs are only kept for up to 30 days. This is from the date the entry was sent to the server. You have 30 days to assess log entries from when they are posted.
If you wish to generate an archive, you can do so by clicking the ‘Generate Archive’ button and it will download the last 30 days for you as a CSV file.
