AlertBot Knowledge Base
Go to website
Back
Articles on:Reports
No description

Categories

  • Status Page
  • Problems & Errors
  • Reports
  • Alerting
  • Monitors
  • Setup & Signup
  • Technical
  • Service Notes
  • Billing
  • Account
  • CentralPass
Test Report
  • Waterfall Report Components Explanation
    DNS: This is the time it takes our test station to request the DNS information from the web server hosting the files' DNS provider and for that DNS provider to return the information back to our test station. If no DNS time is listed, it means that our test station already looked up the DNS at some point earlier during this test. This is to be expected. TCP Open: This is the time that it takes our test station and the server that is hosting the file to establish a valid TCP connectiFew readers
  • Waterfall Report
    The Waterfall Report is an advanced report available for our transactional monitors. This report provides detailed information which includes: the DNS lookup time, TCP connect time, time to first byte, transfer time, file size, HTTP status, and the source IP address of every URL encountered during a test. This data is displayed in both a waterfall graph and in a detailed list. A Waterfall Report is displayed after every On-Demand test and is automatically saved in the Test log and FailuFew readers
  • How is Old Performance Data Compressed?
    Test Results that are older than 28 days are compressed into a summary form. This summarized form affects your data in the following way: Failed-Test Data is Never Compressed - we never compress any of the performance data for failed tests. We know that this data is important to you and therefore we keep an unaltered and accurate history of every individual failure. Passed-Test Data Compression - we take all of the performance data for good tests and compress it by reSome readers
  • What Time Interval Will My Reports and Data be Displayed In?
    We display screenshots of the different types of reports that are available to our users. While these reports are displayed in different time intervals on our website, the reports that are generated for individual users will correspond to their specific monitoring services. Monitoring data and corresponding reports will be displayed in the same time interval as your monitoring service. For example, if you are running a website monitor at a 5 minute interval, your data and reports will aSome readers
  • Reasons for Time Compression
    Data is compressed in order to greatly increase reporting efficiency and performance. As data is compressed, some of the precision is lost, but this allows AlertBot to retain greater quantities of data, making it more useful, yet keeping the data manageable. More detailed information about how time and data are compressed can be found in the related article below entitled: "Time Compression" Related Links Time Compression (https://abkb.crisp.help/en-us/article/time-compressioSome readers
  • How Long are Test Results Kept?
    Test Results records older than 28 days only contain tests collected during failure events. Older passed tests are discarded. Summary data for passed tests older than 28 days is, however, still available in our Reporting Charts section. For a description of how Test Results are compressed, see the related article below. Related Links How is Old Performance Data Compressed?Some readers
  • Time Compression
    Data is compressed in 4 ways: Hourly data is the average of all of the test results from that single hour of testing. Daily data is the average of all of the test results from that day. Weekly data is the average of all of the test results from that week. Monthly data is the average of all of the test results from that month. Test data is compressed in relation to how long ago the test was run. Since minute details of newer data are much more important than the small detaSome readers
  • Time Compression Cutoff Times
    The times that the compression intervals are evaluated at are determined at 12:00 UTC. The offset that you are observing is due to your time zone in relation to UTC. For instance, if you are located on the East Coast of the United States, your local time is UTC - 5 hours. If it is April 5th, 2005, the 28 days of hourly data will begin at March 7th, 2005 at 7:00 PM, your local time, instead of March 8th, 2005 at 12:00 AMSome readers
  • Report & Chart Time Compression
    As time progresses, data is compressed in order to greatly increase reporting efficiency and performance. Because of data being compressed into different time blocks, if you request data with a time span that overlaps a compression change, the data may be displayed in the chart differently than what you expected. For instance, if you create a chart to display statistics on an hourly basis spanning more than a month (which would overlap the change in compression from hourly to daily compFew readers
  • Extended Data Storage
    Extended data is discarded 28 days after the date of the test that recorded it. Extended data is any additional information that is kept and stored along with the normal results that are contained in a test. Extended data currently includes screenshots of the page encountered during an error, and the full URL and IP Address of the file that the error was associated with. Do note that the generic error message associated with a failure is never discarded and never compressed. For deFew readers
  • Automatically Emailed Status Reports
    AlertBot automatically emails a weekly Status Report. This email report includes all monitors on your account. By default, the weekly automated report is sent to the email address registered as your account holder. If you'd like to add recipients to receive the weekly automated email report, please contact Help Desk for assistance. If you would like to opt out of receiving the weekly automated email report, please either reply to the ReportFew readers

Not finding what you are looking for?

Chat with us or send us an email.

  • Chat with us
  • Send us an email
© 2025 AlertBot Knowledge Base