Skip to content

Commit 8b0b223

Browse files
Update troubleshoot.md
1 parent 7290fd0 commit 8b0b223

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/internet-analyzer/troubleshoot.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,14 @@ ms.author: dibotero
1414
This article contains troubleshooting steps for common Internet Analyzer issues.
1515

1616
## Azure Portal
17-
**"Not enough measurements have been collected for this scorecard" in the Scorecards section**
17+
**"A scorecard hasn't been generated for the selected End Date" in the Scorecards section**
1818

1919
Note that:
20+
- Scorecards are generated on a daily basis (at the end of every day, UTC time).
21+
- Scorecards are only generated if more than 100 measurements were collected for the selected filter combination (Test, Time Period, Country, etc.).
2022
- The client script must be embedded into an **HTTPS** website. Measurements won't be collected if the script runs in a plaintext (**http://**) or local (**file://**) website.
2123
- Measurement data will only be collected if the Internet Analyzer profile's client script has been embedded into an application that is receiving real user traffic. Synthetic traffic (for example, Azure WebApp Performance Tests) does not typically execute embedded Javascript code, so no measurements will be generated by that type of traffic.
2224
- Time series are generated once an hour, so you’ll need to wait at least that amount of time for new measurement data to show up.
23-
- Scorecards are generated on a daily basis (at the end of every day, UTC time).
24-
- Scorecards are only generated if more than 100 measurements were collected for the selected filter combination (Test, Time Period, Country, etc.).
2525

2626
## Next steps
2727
Read the [Internet Analyzer FAQ](internet-analyzer-faq.md)

0 commit comments

Comments
 (0)