The table below summarizes the key monitoring types available for Dotcom-Monitor users and helps you select the right one based on your specific needs.

 

Monitoring Type Description When to Use Key Features
Multiple Step Process Simulates user interactions (e.g. form submissions, searches) using a real browser. To monitor complex web applications in real browsers.
  • Real browser-based
  • Validates page load time and rendering at each step
  • Detects user-flow issues
Single Web Page Monitoring Loads and checks a single web page in a real browser session. To monitor basic page availability and speed.
  • Browser-level accuracy
  • Validates the initial page load and rendering
HTTP(S) Monitoring Sends HTTP/HTTPS requests to check service or site responses. Best for simple uptime or availability monitoring at the server level (status codes, headers, basic content).
  • Works without a browser
  • Inspects server responses
  • Does not execute JavaScript or load page resources
API — Web Services Monitoring Verifies expected server response codes like 200 OK or 404 errors. For fast, backend-level monitoring of APIs or server endpoints.
  • Checks connectivity and status codes
  • Doesn’t detect front-end issues
Protocols — Infrastructure Monitoring Monitors non-browser services like FTP, SMTP/POP3/IMAP, DNS, streaming, etc. For monitoring backend services on your servers or network devices.
  • Service-specific checks
Performance Counters — MetricsView Monitors server and device resource usage (CPU, memory, disk, etc.). To make sure servers don’t run out of disk space or memory.
  • Prevents outages
  • Real-time insights
  • Ideal for network and server health