Troubleshooting User Timings
There are a few reasons why a user timing may not appear in Rigor. Test in your own browser to make sure that the mark or measure is logged as you expect before continuing:
The user timing you're looking for occurs after Fully Loaded Time
Rigor collects data for user timings at Fully Loaded Time, so metrics that are logged after are not recorded. This also means user timings that are logged as the result of a user interaction like clicking a button or filling in a form are not recorded.
To check if this is the reason why your metric is not appearing in Rigor, you can download the HAR file for the check in question via the run results.
If the HAR does not include the metric you're looking for, Rigor was not able to record that metric. If the HAR does include the metric, continue reading for other possible explanations.
Your check has reached the limit of 100 user timings
Rigor stores the first 100 user timings logged per check for trending, alerting, and aggregating. If a user timing is missing in Rigor, your check may have reached this limit.
This can happen when:
- Your site logs more than 100 unique user timings during a typical page load
- Your CDN logs additional metrics. Some CDNs add timestamps to metric names, which can quickly add towards the limit
- You have changed your check configuration to monitor a new site with different metrics, or you have changed the names of your user timings. This means the list of metrics Rigor is looking for is out of date
To learn more about how to create user timings for Rigor to collect, check out this documentation from Mozilla.
If you would like to reset or replace the user timings Rigor is logging, please reach out to firstname.lastname@example.org.