> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring External Assets with Uptime Monitors in MSP Process

> The Uptime Monitors module in MSP Process lets you monitor external customer assets by IP address or FQDN. This is useful for tracking the availability of…

The **Uptime Monitors** module in MSP Process lets you monitor external customer assets by IP address or FQDN. This is useful for tracking the availability of firewalls, websites, public services, and other internet-facing systems. Uptime Monitors are part of the **Pro plan** and can help replace standalone tools, such as Pingdom or other uptime monitoring platforms.

## Where to find Uptime Monitors

1. In MSP Process, open the **Monitor & Notify** menu from the left sidebar.
2. Select **Uptime Monitors**.

![](https://mintcdn.com/triggr/2kaOQdWPjLF3xX8p/images/msp-process-kb/1de726ad309f.gif?s=2fd09d95641afcad90474c082d994bc7)

![](https://mintcdn.com/triggr/o9r5jEtjdR2oUtiW/images/msp-process-kb/e5b732672fda.gif?s=1787851be8130061a0e746638fa30f01)

## Create a new uptime monitor

Creating a monitor is straightforward. You can assign it to a company, optionally enter a site, choose the scan interval, define the scan type, and specify which Azure region should perform the check.

1. From the **Uptime Monitors** page, click **+ Create**.

![](https://mintcdn.com/triggr/o9r5jEtjdR2oUtiW/images/msp-process-kb/d9e7ea229c25.png?fit=max\&auto=format\&n=o9r5jEtjdR2oUtiW\&q=85\&s=07bbc802356fb0d3150b854785f3fdcd)

1. Select the **Local Company** the monitor should belong to - you'll set those up under the **AI Service Desk -> Ticketing -> Company Mapping** page.

![](https://mintcdn.com/triggr/o9r5jEtjdR2oUtiW/images/msp-process-kb/deaf61bef714.gif?s=61ab72a805d917723472042c0b76ece5)

1. Optionally enter a **Site**, such as **Main Office**.

![](https://mintcdn.com/triggr/2kaOQdWPjLF3xX8p/images/msp-process-kb/0db2206634c5.png?fit=max\&auto=format\&n=2kaOQdWPjLF3xX8p\&q=85\&s=962e9ecfd6fdd86df3bef36da0041e43)

1. Enter a descriptive **Device Name**, such as **External Firewall**.

![](https://mintcdn.com/triggr/-njaXAnAb5AWpJCy/images/msp-process-kb/7179209104b3.png?fit=max\&auto=format\&n=-njaXAnAb5AWpJCy\&q=85\&s=20a34058b33329538d3b58fddbf94405)

1. Choose the **Period \[min]** for how often the monitor should run. The default (and minimum) interval is **5 minutes**.
2. Select the **Type** of check you want to perform.

![](https://mintcdn.com/triggr/o9r5jEtjdR2oUtiW/images/msp-process-kb/b02b762b9b2b.gif?s=fc8007bb157f6072ec4c06de43360e9d)

## Available monitor types

MSP Process supports several ways to test external availability, depending on what you need to monitor.

* **Port checks** for common services such as HTTP, HTTPS, FTP, SMTP, POP3, and IMAP
* **Custom port** checks for other externally exposed services
* **HTTPS checks** for web endpoints
* **Ping** for basic reachability testing

![](https://mintcdn.com/triggr/qgn0c5cLkGKqcauq/images/msp-process-kb/85ba968dd5a4.gif?s=7ce15583c419c3c12e221256875ca2e2)

If you only need to confirm that a public IP responds, **Ping** is often the simplest option.

![](https://mintcdn.com/triggr/2kaOQdWPjLF3xX8p/images/msp-process-kb/3860644a9911.gif?s=e9efbbacbd9266953e35ad1dec726e95)

## Choose the scan region and target

After selecting the monitor type, choose where the check should originate and enter the public target you want to monitor.

1. Select the **Server region**. MSP Process provides scanning probes in:
2. **Central US** (Azure)
3. **Western Europe** (Azure)
4. Enter the public **IP address** or **FQDN** in the **URL** field.
5. If desired, enable **Request from another region if current failed** so MSP Process can retry the check from the alternate region when the primary region fails.

##

## Test and create the monitor

1. Click **Test** to validate the settings and confirm the target responds as expected.
2. Once the test looks correct, click **Create**.

## Bulk import monitors with CSV

If you need to create many monitors at once, you can use the **Upload** option on the Uptime Monitors page to import them in bulk.

* Download the provided **CSV template**
* Populate the file with your monitor details
* Upload the completed CSV to create multiple monitors at once

This is helpful when onboarding many customer sites or migrating from another monitoring platform.

## View monitor results and status history

After monitors are created, you can review their status from the Uptime Monitors list. Click the **magnifying glass** icon for a monitor to open a detailed view showing:

* Current status
* Uptime percentage
* Recent events
* Historical availability information
* How frequently outages or recoveries have occurred

The overview page is useful for both day-to-day monitoring and troubleshooting intermittent external issues.

## Use TV Mode for NOC displays

If you want to display uptime information on a wallboard or NOC screen, you can switch the detailed monitor view into **TV Mode**. This mode automatically refreshes and provides an at-a-glance dashboard for ongoing monitoring.

## Getting Notified When an Uptime Monitor Fails

When an Uptime Monitor fails, you can configure MSP Process to generate a ticket in your PSA, and/or send out an Email, SMS, Voice, Slack or Microsoft Teams alert. To get started, go to the **Monitor & Notify -> Workflows** page, and then click on the **Uptime Monitor Workflows** tab:

![](https://mintcdn.com/triggr/-njaXAnAb5AWpJCy/images/msp-process-kb/4223288a6128.webp?fit=max\&auto=format\&n=-njaXAnAb5AWpJCy\&q=85\&s=fbdeff122a434f4aebc3b592967da0cd)

* To get notified on a specified Uptime Monitor, click the **Create** button
* To get notified on all of the Uptime Monitors within a Company, click the **Create Group** button

## Tips and best practices

* Use clear, descriptive monitor names so technicians can quickly identify the asset being tested.
* Assign monitors to the correct **company** and **site** for easier reporting and filtering.
* Use **Ping** for simple reachability checks and **Port** or **HTTPS** checks when you need to verify a specific service.
* Enable the *Request from another's region* retry when you want additional confirmation of an outage.
* Use CSV import for larger deployments.

##

## Summary

Uptime Monitors in MSP Process provide a simple way to monitor external IPs and FQDNs for customer assets. You can create individual monitors in just a few clicks, bulk import them with CSV, review detailed status history, and display results in TV Mode for NOC visibility. For broader notification workflows in MSP Process, you may also want to review Notification Groups and Scheduling Setup and [Notifying On Specific Ticket Details](https://kb.mspprocess.com/msp-process/monitor-notify/data-ingestion-workflows/notifying-on-specific-ticket-details.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.