The sections below describe how to identify the activities of the main processing pipeline through the Portal. In some cases, additional troubleshooting may be required outside of the Portal.
Monitoring current activities
In the Portal, the Active menu contains useful tools for assessing the current activities in Experience Analytics.
- Active Status: Displays status information on current activities on the web
- Verify that the Generation time statistics seem valid.
- Check the Error counts. Large error counts can be investigated by creating a report to track the application error.
- Active Sessions: Displays information on active sessions. If there are no active
sessions, go to the monitored web application and begin browsing to create one.
- There may be a delay of 90 seconds on average before your active session begins appearing in this report.
- If you still see 0 active sessions after creating an active session, then see the "No current activity" section, below.
- Active Events: Displays information on the currently active events for the selected
- This report may contain useful information on cumulative events over approximately the last 30 minutes. If you have created events to occur on every page or on every session, you can look for those events to gauge basic activities.
- These canister events are accessed through Search Server and bypass the Experience Analytics database. If there is no data in this report, then there may be a problem with Search Server.
- If you have created events to monitor specific application errors or issues with the monitored web application, you may find the Watch feature useful.
- To review active sessions containing the event, click the hyperlink number in the Live Count column.
- To see all active events as a list, select
Listfrom the View drop-down.
- Alert Monitor: Displays status of the currently configured set of alerts.
- The Alert Summary panel indicates Warning and Alert Threshold values as well as the current
value, which may be useful for identifying either significant problems in the system, depending on
the alert, or a misconfigured alert.
- When an alert is selected, search links in the displayed report provide access to active sessions or recently completed sessions that contain events that triggered the alert.
- Recent alert history is available for download.
- Since alerts are triggered based on events, you can create events to report useful information on the current state of the page or session.
- To view a dashboard of the currently active alerts, click View Gallery. You can drill into these summary reports on each alert for additional detail.
- The Alert Summary panel indicates Warning and Alert Threshold values as well as the current value, which may be useful for identifying either significant problems in the system, depending on the alert, or a misconfigured alert.
No current activity
If you have been unable to detect any current Experience Analytics activities, including no active sessions after you have generated one, it indicates that sessions are not reaching the Short Term Canister.
The first test is to verify through the TMS Pipeline Status tab that the pipeline is processing hits.
- Login to the Portal as an administrator.
- Navigate to TMS.
- Click the Pipeline Status tab.
- From the Server drop-down, select the Processing Server to test.
- Select the appropriate pipeline from the Pipelines textbox.
- In the upper-right corner, for the selected pipeline on the selected server, you can review the
data flow through the individual session agents in the pipeline.
- Data should be flowing consistently through all listed session agents.
- Some session agents, such as Data Drop, remove hits from the pipeline. Among the list of session agents, the numbers in the Hit Count column may decrease.
- The Queued column indicates hits that have been queued for processing for the listed session agent. Typically, this situation indicates some misconfiguration of the session agent. In such cases, you should review the session agent's configuration.
- Check the other pipelines on the selected server, if applicable.
- Check the pipelines on other servers in the environment, if applicable.
If hits are getting bottlenecked with a specific session agent, then review the session agent's configuration.