Data Monitored for Websites

Last updated on 26 April, 2024

The metrics collected for a website depend on whether the website is monitored by a Web Check or Ping Check. You can view the collected data in the Website’s Graphs and Raw Data tabs. 

The Websites page displays the Web Check or Ping Check data based on the following checkpoints:

  • Per-checkpoint basis—Displays the data for the selected checkpoint locations
  • Overall checkpoint basis—Displays the overall aggregated data for the different checkpoint locations 

Note: In addition to viewing website metrics on the Graphs and Raw Data tabs for a website, you can also view these metrics from your dashboards. For more information on adding website metrics to your dashboards, see Widget Overview.

Data Monitored for Web Checks

For each checkpoint configured in your Web Check (whether an external LogicMonitor checkpoint or internal Collector), the following data is monitored:

  • Response time—The time (milliseconds) it takes to run the entire Web Check is available per checkpoint location, both visually in graph form on the Graphs tab (Response Time graph) and as columnar data on the Raw Data tab.
  • Status—The status of the Web Check (okay and timeout) is available per checkpoint location, both visually in graph form on the Graphs tab (Status graph) and as columnar data on the Raw Data tab. For more information on various status codes LogicMonitor returns for Web Checks, see Understanding Website Status Codes.
  • Read time—The total time (milliseconds) spent reading all data sent back by the server, from the first to the last byte. This data is available per checkpoint location, both visually in graph form on the Graphs tab (Initial Connection Performance graph) and as columnar data on the Raw Data tab. Only the read time for the first step of a Web Check is collected.
  • Wait time—The server-side process delay (milliseconds). This data is available per checkpoint location, both visually in graph form on the Graphs tab (Initial Connection Performance graph) and as columnar data on the Raw Data tab. Only the read time for the first step of a Web Check is collected.
  • SSL handshake time—The time (milliseconds) spent negotiating the SSL handshake, including certificate exchange and validation. This data is available per checkpoint location, both visually in graph form on the Graphs tab (Initial Connection Performance graph) and as columnar data on the Raw Data tab. Only the read time for the first step of a Web Check is collected.
  • SSL status—The status of the website’s SSL environment (okay and expired certificate) is available per checkpoint location as columnar data on the Raw Data tab. For a description of the various status codes LogicMonitor returns for SSL status, see Understanding Website Status Codes.
  • Connect time—The time (milliseconds) required to establish the socket connection, including the SYN/ACK negotiation. This data is available per checkpoint location, both visually in graph form on the Graphs tab (Initial Connection Performance graph) and as columnar data on the Raw Data tab. Only the read time for the first step of a Web Check is collected.
  • DNS resolve time—The time (milliseconds) required to resolve the DNS, including the time required to contact the DNS server if necessary. This data is available per checkpoint location, both visually in graph form on the Graphs tab (Initial Connection Performance graph) and as columnar data on the Raw Data tab. Only the read time for the first step of a Web Check is collected.

In addition to viewing data on a per-checkpoint basis, there are a few metrics offered that provide a view into the health of the Web Check overall (aggregated across all checkpoint locations):

  • Overall status—If no checkpoint locations return an error, LogicMonitor returns an overall status code of “1.” If an error at one or more checkpoints is detected, LogicMonitor returns an overall status code of “2.” Overall status is available both visually in graph form on the Graphs tab (Website Overall Status graph) and as columnar data on the Raw Data tab. To get more specific information about an overall status error, you’ll need to review the Web Check status codes for the individual test locations.
  • Overall SSL status— If no checkpoint locations return an SSL error, LogicMonitor returns an overall status code of “1.” If an error at more than one checkpoint is detected, LogicMonitor returns an overall status code of “2.” Overall SSL status is available as columnar data on the Raw Data tab. To get more specific information about an overall SSL status error, you’ll need to review the status codes for the individual test locations.
  • Total site monitor count—The number of checkpoints that participated in the check. This count is available as columnar data on the Raw Data tab (totalSmCount).
  • Failed site monitor count—The number of checkpoints that failed in the check. This count is available as a columnar date on the Raw Data tab (failSmCount).
  • Reporting timestamp—The timestamp (seconds) when the site monitor reported the data. This count is available as a columnar date on the Raw Data tab (reportlSmEpoch).

Data Monitored for Ping Checks

For each checkpoint configured in your Ping Check (whether an external LogicMonitor checkpoint or internal Collector), the following data is monitored:

  • Trace route—In the Trace Route tab, you can see the list of host names or IP addresses test packets are routed through from the originating test checkpoint to the destination host name or IP address (live data capture only for troubleshooting purposes; trace route information is not stored for historical purposes).
  • Status—The status of the Ping Check (okay and DNS failure) is available per checkpoint location, both visually in graph form on the Graphs tab (Status graph) and as columnar data on the Raw Data tab. For more information on the various status codes LogicMonitor returns for Ping Checks, see Understanding Website Status Codes.
  • Maximum, minimum, and average round trip times—The maximum, minimum, and average round trip times (RTT) for packets in the Ping Check are available per checkpoint location, both visually in graph form on the Graphs tab (Response Time graph) and as columnar data on the Raw Data tab.
  • Number of sent and received packets—The number of packets sent and received in the Ping Check is available per checkpoint location, both visually in graph form on the Graphs tab (Ping Statistics graph) and as columnar data on the Raw Data tab.

In addition to viewing data on a per-checkpoint basis, there are a few metrics offered that provide a view into the health of the Ping Check overall (aggregated across all checkpoint locations):

  • Overall status—If no checkpoint locations return an error, LogicMonitor returns an overall status code of “1.” If an error at more than one checkpoint is detected, LogicMonitor returns an overall status code of “2.” Overall status is available both visually in graph form on the Graphs tab (Website Overall Status graph) and as columnar data on the Raw Data tab. To get more specific information about an overall status error, you’ll need to review the Ping Check status codes for the individual test locations.
  • Total site monitor count—The number of checkpoints that participated in the check. This count is available as columnar data on the Raw Data tab (totalSmCount).
  • Failed site monitor count—The number of checkpoints that failed in the check. This count is available as a columnar date on the Raw Data tab (failSmCount).
  • Reporting timestamp—The timestamp (seconds) when the site monitor reported the data. This count is available as a columnar date on the Raw Data tab (eportlSmEpoch).
In This Article