Monitor a Site

Before creating a monitor you should decide what to monitor. latency can monitor your website or service but that's old news. Maybe you've just launched a new social campaign across Instagram/Facebook, or maybe your website plays a collection of hosted YouTube videos. This is where latency can help you.

All monitors have the ability to select an optional service to alert you about issues. These are triggered by official provider status pages and

Monitors within Latency consist of several parts (tasks, schedules, alerts), which form a configuration set for each piece.

To create a basic monitor for a website via CLI you can run the following:

$ latency monitor https://google.com

A TCP monitor will be created for the Google homepage on port 443 automatically.

You can monitor just IP addresses too:

$ latency monitor 1.1.1.1

The monitor command is quite opinoinated based on input. Any time an IP is passed, ICMP will be assumed, and if a hostname is passed TCP will be used by default.

This can be overriden:

$ latency monitor https://google.com --with.icmp

Or check a specific port on an IP with ICMP:

$ latency monitor 1.1.1.1:443 --with.icmp

Using the --with.* flags you can indicate what sub-tasks you would like to run along with your monitor.

Read more about tasks to learn about what you can run and how to create your own.

By default monitors run once every minute but this too can be configured:

$ latency monitor 1.1.1.1 --interval=120
# can use m, hr, d, wk, mo, y
$ latency monitor 1.1.1.1 --interval=30m

If you're logged into Latency you can also set an alert contact when adding a monitor:

$