Why Is Data Missing?

There may be a number of reasons why you may be noticing missing some data from tests. Although Niteco Performance Insights will reliably run your tests when scheduled, it may not have been able to calculate metrics at specific time causing missing data, which can affect the accuracy of synthetic tests and performance assessments. This section explains common causes of missing data, troubleshooting methods, and preventive measures to ensure comprehensive data collection.

Common Causes of Missing Data

Network Issues
Intermittent network issues can result in incomplete data transmission during synthetic tests. If the server hosting your website or application experiences slow connection speeds on its network or is down due to maintenance or other issues (e.g. DDoS attacks) our system will not be able to connect to your server and this will result in a failed tests or incomplete data. If you have experienced a failed test or loss of data at a specific time, try to find out your server's status at that point in time to see if it was experiencing difficulties and if they are resolved. Use network monitoring tools to evaluate the stability and speed of your network during test execution.
Server Configuration Issues
Improper server settings can lead to failures in data collection from synthetic tests. Our tests may be blocked by your server because of Firewalls, Bot managers or any other measures undertaken by your server to prevent automated traffic to your server. Check your server WAF (Web Application Firewall) settings or any Bot Manager settings you have to find out if they are blocking requests from specific sources..
Script Failures
Errors in the synthetic test scripts you have added to your tests can cause potential errors and missing data. Please check that scripts do not cause errors in your webpages to avoid problems that could cause failed tests and loss of datapoints.
Rate Limiting
Servers may limit the amount of page or/and api requests that can be made in a certain amount of time. If tests run cause this limit to be reached the server may reject the request, leading to failed tests or missing data.