Use the following troubleshooting table to find solutions to common problems with installation and configuration of cxOverstat.
The following table lists corrective actions to some of the common problems that might occur after you install and configure cxOverstat.
Symptom | Action |
---|---|
The Overlays menu option in BBR cannot be selected when you view a page that has the cxOverstat UI SDK enabled. |
Make sure that the browser you are using to replay the session supports HTML5. If you are viewing a mobile session, you must have CX Mobile license. |
cxOverstat is capturing data from bots. | You can filter traffic from bots by editing the Step - Usability Event Filter [BB] event.
|
The row count for the Step - Target
ID dimension is growing at a fast rate when compared to other dimensions in the database group. |
Monitor the growth rate by logging in to the Portal, then select System > Database Table size > Dimension for the Data Group. If the growth rate does not stabilize, examine the target IDs to begin the troubleshooting process. If new element IDs are constantly generated on a web page, Step - Target ID captures each new ID. |
Overlays for web pages that have dynamic URLs are not loading in BBR. | The Step - ScreenView URL dimension uses the original URL for the captured web page in place of using TLT_URL , which can prevent BBR from locating and displaying web pages that use dynamic URLs. |
Logging
cxOverstat log messages are written into the Portal log file. The file is in the following location on the Portal Server:
<install_directory>\Logs\TLPortal_YYYYMMDD.log
where YYYYMMDD
is a date stamp.