Troubleshooting - Data Collector

Use the information in this section to troubleshoot Data Collector.

Data collector messages that you can ignore
When the SQL Server is rebooting or has entered a maintenance mode, specific messages are written to the Portal Data Collector log. In most cases you can ignore these messages.
Addressing Data Collector performance issues
This section provides information about how to begin troubleshooting the Data Collector's performance.
What happens to statistical data if the Data Collector Service or reports database goes down?
Every time events fire in a Processing Server, the Canister datastore on that Processing Server creates one or more records. In a functioning system, the Report Data Collector (RDC) service collects these data from every Processing Server and stores the information in the reports database.
Mismatches between counts in event charts and counts in drill-down searches
In an event chart or dashboard, the event counts for a given period may be reported. When you click the link to drill down to the underlying sessions, the number of returned sessions differs from the number reported in the chart.
What to do when the Data Collector cannot connect to the Canister
There might be times when the Data Collector cannot connect to the Canister, resulting in messages to the log file as shown here.
SQL exception "Connection reset by peer: socket write error" in event log
This error may occur when the Tealeaf Report Data Collector service is trying to communicate with SQL Server running on a remote server. It indicates that the remote SQL Server did not respond to the request by the Report Data Collector service to insert data. The error condition could be either network or SQL Server related.
What to do when the Database Filegroup Report shows no data even though the database tables contain data
After an installation, the Database Filegroup Report does not display data, even though the database tables contain data. Use the information here to troubleshoot this issue.

Parent topic: Troubleshooting Tealeaf databases