MONITORING
Historical Response-Time Monitoring
Query recent monitor results for a target configured by the site administrator.
39DExternal testRuns from the toolbox server
RUN TEST
Historical Response-Time Monitoring
HOW IT WORKS
About the Historical Response-Time Monitoring
The included CLI cron script checks administrator-defined targets and stores status, duration and error details in PDO storage. This page reads recent samples and plots them in the browser.
How to use this result
- Run the test from this server.Use a public hostname, address, prefix or ASN in the format requested above.
- Compare with another observation point.Run a local command or use a second provider to identify location-specific behaviour.
- Correlate related evidence.Use the related tools below to compare DNS, routes, ports, TLS and application responses.
- Keep the time and context.Routing, DNS caches and reputation data change, so record when the result was collected.
Common interpretation issues
- The cron job must be scheduled by the server administrator.
- A single monitoring location cannot prove global availability.
- Database storage must be writable and protected from web access.
NEED HELP INTERPRETING THE RESULT?
39D supports business networks, cyber security and managed IT.
For ongoing support or a larger infrastructure project, speak to the 39D team.
Frequently asked questions
Can visitors add monitors?
No. Targets are controlled in config.php to prevent public users creating ongoing workload.
How often should cron run?
Five-minute checks are a common starting point, but choose a cadence suitable for your server and monitoring needs.