Complete the following tests to verify that these services are operational.

1. In the Portal menu, navigate to TMS.
2. In TMS WorldView, select View > Servers.
3. Select the server hosting the Data Collector.

   The icon next to the Data Collector should be green. If it is not, to start the Data Collector, select it and click Start. When it restarts, the icon becomes green again, and the Data Collector resumes polling the LTC at the appropriate interval.

   If the appropriate services are working, continue with the next section.

1. In the Portal menu, select Analyze > Report Builder.
2. Change Focus to today's date, if it is not currently selected.
3. Through the Report Builder, you can open the activity reports. Click the Open icon. The names of all activity reports begin with Activity Report:.
   • Traffic (MB) - Indicates overall processing for the selected period.
   • Round Trip - Provides information on the round trip times for data for the selected period.

   These reports are all powered by the Tealeaf database. If data is present in these reports, then the Data Collector is able to collect and store data.

• If you do not see data in these reports for the currently selected date. Then, you should change the focus date to just the preceding date and re-review the reports. In this manner, you can step backward until you locate the date when the Data Collector stopped processing.
• If you do see data in these reports, but the data seems to be low, continue with the next section.

You can use event charts to monitor Data Collector performance. An event chart is generated by querying the database for the number of instances of an event for the specified time period. For example, you can generate an event chart for an event that occurs every session or on every page to provide indicate when the Data Collector is gathering data. Since event charts typically break down the reporting period into hourly periods, you can check to see when the most recent data is displayed in the event chart. Please complete the following steps.

1. In the Portal menu, select Analyze > Report Builder.
2. Change Focus to today's date, if it is not currently selected.
3. From the Event Selector, select an event that occurs every page or every session and click Select.

   For example, if your web application uses a Session Start event or always begins with a Login page, a related event can be selected for this test.

   Note: Depending on traffic load and processing resources, creating an event that is triggered on every page may be problematic. If your system can handle the load, one example of an event triggered on every page is an event that is fired when the application message HTTP - 200 is in the response. Since this message is part of every response, it is a valid event to test.
4. If the report does not automatically refresh, click Refresh
5. In the displayed report, compare the time for the most recently displayed bar in the bar graph to the local system time.
   • Any discrepancies between the hour in the bar chart and the current hour in your time zone indicates that there may be a general data flow problem in the main processing pipeline.
     • If you have already completed the preceding steps on this page and have not found the source of the issue, you may infer that the problem is with the Data Collector. Further analysis is required.
     • You can compare the event count value in this report to the count among active events.
   • If there are no differences, you might check the Count of events in the most recent hour in the displayed table to verify that the count is within reason.
   • To retrieve a list of sessions where the selected event was triggered within an hour, click the time indicator for the hour period.

1. In the Portal menu, navigate to Portal Management.
2. Under Servers, click Manage Servers.
3. Select the server where the Data Collector is installed. By default, this server is the Report server.
   The server-specific toolbar is displayed at the top of the pane.
4. Review the timestamps by opening the Collector Dates tool from the toolbar.
   A set of statistics is displayed.
5. Review the event logs by opening the Windows™ Event Log tool from the toolbar.
   1. In the Event Log viewer, you can select the following values to begin your troubleshooting of the Data Collector:
      • Type: Application
      • Severity: Error
      • View: depends.
   2. Review the list of Application errors to determine if any involve the Data Collector. If you find specific errors, the log files may provide additional detail.
   3. If you cannot find specific errors for the selected parameters, you can expand them to include non-Error events over a large time period, as necessary. In rare cases, you may need to review System Type errors.
6. Review the text logs by opening the Logs tool from the toolbar.

   The logs for all Tealeaf services installed on that machine are available in the bottom panel.

   1. Filter the display to show only the Data Collector logs.
   2. Search the log for ERROR in caps.
      Note: In the Data Collector log, there may be fact names with ERROR in them. These may not be errors.