| 292 | You could also use the ''' "probe = EchoPingHttp" ''' statement once for host1, and then this would be the default probe until another "probe = " statement is seen in the Targets file. |
| 293 | |
| 294 | You can add more host entries if you wish, or you could consider checking the latency on remote machines - these are likely to be more interesting. Machines such as your own publicly accessible servers are a good choice, or, perhaps other web servers you use often (Google, Yahoo, Government pages, stores, etc.?). |
| 295 | |
| 296 | For example, consider adding something like this at the bottom of the Targets file: |
| 297 | {{{ |
| 298 | # |
| 299 | # Remote Web server response |
| 300 | # |
| 301 | |
| 302 | +HTTPSRemote |
| 303 | |
| 304 | menu = Remote HTTPS Response |
| 305 | title = HTTPS Response Remote Machines |
| 306 | |
| 307 | ++google |
| 308 | |
| 309 | menu = Google |
| 310 | title = Google.com HTTPS response time |
| 311 | probe = EchoPingHttps |
| 312 | host = www.google.org |
| 313 | |
| 314 | ++learn |
| 315 | |
| 316 | menu = LEARN |
| 317 | title = LEARN HTTPS response time |
| 318 | probe = EchoPingHttps |
| 319 | host = www.learn.ac.lk |
| 320 | |
| 321 | ++youtube |
| 322 | |
| 323 | menu = Youtube |
| 324 | title = Youtube HTTPS response time |
| 325 | probe = EchoPingHttps |
| 326 | host = www.youtube.com |
| 327 | }}} |
| 328 | |