What is a monitor

Monitors are one of the core pieces in Uptinio. They represent a Network Monitor Check where it can be the following type of requests

  • HTTP/HTTPs
  • TCP
  • Ping
  • Keyword
  • Heartbeat

General Properties

There are some common properties shared across all monitors, which include

Property Name Description Default value
Name Optional name to assign, this is mostly utilized to identify each monitor null
Monitor interval Frequency in minutes for your monitor to run 1
Integrations Used for alerting, choose the integrations you want to notify if your monitor has an incident. null
Request Timeout Number of seconds for the request to timeout 30

Monitor Types

There are various types of monitors, and each one of them has its own use cases. This guide won’t go through each use case, but showcase what are the strengths and properties for each one of them.

HTTP/HTTPs

This is the most common Monitor, used widely to check websites and APIs. This uses the HTTP protocol in order to request information from servers.

On top of this. This monitor is used to monitor SSL issues and Doman name expiration. Both of these tend to go along HTTP checks. These are enabled by default.

Additional properties

Property Name Description Default value
Check SSL errors Set to true if you want to monitor SSL errors and expiration dates true
Domain expiry reminders Set to true if you want to get alerted when a domain is about to expire true
Follow redirections Set to true if you want to follow redirections true
Up HTTP status codes Valid status code to consider monitor as healthy 2xx, 3xx
Auth type Set this up if you have basic authentication on your webserver None
HTTP Method HTTP method utilized to perform the request HEAD
Request body payload to send on the request None
Send as json Set to true if you want to send the Request Body as application/json false

TCP

The TCP Monitor is used to verify the availability of specific services by connecting directly to a specific TCP port on a server. This is especially useful for monitoring applications like databases, mail servers, or other services running on custom ports.

On top of this, the TCP Monitor can provide insights into service latency and availability. No additional configuration is needed beyond specifying the host and port, making it a straightforward option for service monitoring.

Ping

The Ping Monitor checks the network connectivity and response time of a server using ICMP (Internet Control Message Protocol). This monitor sends echo requests to the server and measures response times, giving you a quick snapshot of latency and packet loss.

This monitor is ideal for simple reachability checks and network diagnostics. It’s a fast and effective way to ensure that a server or device is online and responsive.

Note: make sure the server is reachable through the internet.

Keyword

The Keyword Monitor is designed for more targeted content verification on websites and applications. It checks a specific page for the presence or absence of a particular keyword or phrase, which is useful for content checks or to ensure specific information is displayed correctly.

For example, you might use this monitor to confirm that a key service message is always visible on your homepage. You simply provide the URL and keyword to be checked.

Additional properties

Property Name Description Default value
Matching keywords Case sensitive keywords to look for, separated by comma. none

Heartbeat

The Heartbeat Monitor is used to verify the regular execution of scheduled jobs, cron jobs, or scripts by expecting periodic check-ins. When a service sends a “heartbeat” signal, this monitor confirms the system is running as expected.

This is crucial for tasks that run at specific intervals and need monitoring for completion or regular execution. Simply set the Monitor interval of check-ins, and Uptinio will alert you if a signal is missed.

Note: The Heartbeat endpoint to ping will be generated once you create the monitor.