The inspection function in the browser is used to investigate issues in the MSPbots app and perform actions such as capturing errors on the page and checking slow network speeds.
This article introduces how to deal with issues when encountering MSPbots pages in Google Chrome and Microsoft Edge browsers.
How to troubleshoot issues using Google Chrome browser developer tools
1. Access Google Chrome browser developer tools.
-
- Method 1: Press Ctrl+Shift+I.
- Method 2: Press F12.
- Method 3: Click on the ellipsis ... in the upper right corner of the screen, then click More tools > Developer tools.
- Method 4: Right-click on a blank area on the screen, then click Inspect.
-
If you'd like to adjust the position of the developer tools, you can click , then choose the appropriate position in Dock side according to the number and size of your browsers.
- Undock into separate window
- Dock to left
- Dock to buttom
- Dock to right
-
- Check Preserve log to maintain the log track when you refresh.
-
For HTTP request type,
-
If the MSPbots page is loading slowly or unresponsive, select All.
-
If a widget or area on the MSPbots page is loading slowly, please select Fetch/XHR. Since the MSPbots API uses Fetch/XHR, we primarily monitor this type of request.
-
- Click on the feature you want to troubleshoot or refresh the page to record the reload.
-
Click Time to adjust the order of time and sort the time it took for the request in descending order.
Description of the log detail grid. You can right-click on the header to customize the columns for display.
* Status - The HTTP response code.
* Status code 200 means the interface request is successful.
* Status code 500 refers to the server side.
* Status code 401 or 403 means insufficient permission to request the API.
* Status code 503 means the server program is being updated and released, and that it is temporarily unavailable. The update will take a few minutes and the user has to try again.
* Type - The resource type. Initiator - What caused a resource to be requested. Clicking a link in the Initiator column takes you to the source code that caused the request.
* Size - This is the size of the data returned by the server. A smaller data returned by the API means that the network transmission time and the waiting time of the user front-end will be shorter.
* Time - How long the request took.
* Waterfall - A graphical representation of the different stages of the request. Hover over a Waterfall to see a breakdown. This includes the total processing time of business programs and databases.
-
After all requests have finished loading, for requests that take longer than 3 seconds or 5 seconds:
- Click the Name of the request.
-
Click Headers > General. Take a screenshot of the General information.
-
In the Headers section, click on Request Headers, take a screenshot containing Tenantcode, Timezoneid, and Token.
-
Click on Payload > View Source, take a screenshot, and copy the statement.
- Click Timing, take a screenshot of the Waterfall breakdown for this request.
- (Optional) If there is at the top right corner of the page, click on it, and then take screenshots of all errors.
If there is a scene you need to record, you can use the tool ScreenToGif to create a GIF and send it to us.
- Access Submit a request – MSPbots.ai to submit a request for us in the Help Center, including these screenshots and the copied statement. After receiving your request, we will process it promptly and contact you. Please wait for our response.
- Close the developer tools.
How to troubleshoot issues using
browser developer tools- Access
- Method 1: Press Ctrl+Shift+I.
- Method 2: Press F12, then select Open DevTools.
- Method 3: Click on the ellipsis ... in the upper right corner of the screen, then click More tools > Developer tools.
- Method 4: Right-click on a blank area on the screen, then click Inspect.
browser developer tools.
-
If you'd like to adjust the position of the developer tools, you can click , then choose the appropriate position in Dock location according to the number and size of your browsers.
- Undock into separate window
- Dock to left
- Dock to buttom
- Dock to right
- Check Preserve log to maintain the log track when you refresh.
-
For HTTP request type,
-
If the MSPbots page is loading slowly or unresponsive, select All.
-
If a widget or area on the MSPbots page is loading slowly, select Fetch/XHR. Since the MSPbots API uses Fetch/XHR, we primarily monitor this type of request.
-
- Click on the feature to troubleshoot or refresh the page to record the reload.
-
Click Time to adjust the order of time and sort the time it took for the request in descending order.
Description of the log detail grid. You can right-click on the header to customize the columns for display.
* Status - The HTTP response code.
* Status code 200 means the interface request is successful.
* Status code 500 refers to the server side.
* Status code 401 or 403 means insufficient permission to request the API.
* Status code 503 means the server program is being updated and released, and that it is temporarily unavailable. The update will take a few minutes and the user has to try again.
* Type - The resource type. Initiator - What caused a resource to be requested. Clicking a link in the Initiator column takes you to the source code that caused the request.
* Size - This is the size of the data returned by the server. A smaller data returned by the API means that the network transmission time and the waiting time of the user front-end will be shorter.
* Time - How long the request took.
* Waterfall - A graphical representation of the different stages of the request. Hover over a Waterfall to see a breakdown. This includes the total processing time of business programs and databases.
-
After all requests have finished loading, for requests that take longer than 3 seconds or 5 seconds:
- Click the Name of the request.
-
Click Headers > General. Take a screenshot of the General information.
-
In the Headers section, click on Request Headers, take a screenshot containing Tenantcode, Timezoneid, and Token.
-
Click on Payload > View Source, take a screenshot and copy the statement.
- Click Timing and take a screenshot of the Waterfall breakdown for this request.
- (Optional)If there is in the Console area, click Console, then take screenshots of all errors.
If there is a scene you need to record, you can use the tool ScreenToGif to create a GIF and send it to us.
- Access Submit a request – MSPbots.ai to submit a request for us in the Help Center, including these screenshots and the copied statement. After receiving your request, we will process it promptly and contact you. Please wait for our response.