# Give everything new a monitor

> New domains, servers and status page components don't come with a monitor. One automation fixes that: switch it on, and everything you add from then on is…

Source: https://infranest.io/docs/monitor-everything-new
Last updated: 2026-10-30

---

This automation makes sure nothing new in your account — a domain, a server, or a status page component — ever goes unwatched. Turn it on once, and InfraNest adds the right monitor automatically every time something new shows up. It's for anyone who wants new infrastructure covered without having to remember to set up monitoring by hand.

## Overview
- Watches for new domains, servers, and status page components, and gives each one a monitor automatically, using the settings you choose.
- A domain gets a website check over HTTPS every minute, plus certificate watching, but only if its DNS shows it actually serves a website. Parked domains, mail-only domains, or domains whose DNS isn't in InfraNest are left alone.
- A server gets a ping check on its public address. Servers without a public address are left alone.
- A status page component named after an address (like *shop.example.com*) is linked to the monitor that already checks that address, or gets a new website check if none exists yet. Components with generic names like *Website* or *API* are left alone, since InfraNest can't tell what to check.
- It never creates a duplicate monitor for something that's already covered. Alerts from these new monitors go to all your usual alert destinations.

<!-- screenshot: monitor-everything-new -->

<!-- docs-screenshots:start:monitor-everything-new -->

![Give everything new a monitor](/media/81ba3baa-dd79-4f25-acff-7ca0c411e18a)

<!-- docs-screenshots:end:monitor-everything-new -->

## Switch on the automation
1. Open **Automations**.
2. Find and choose the recipe **New domain, server or status page component → monitor it** — or click **Set it up** wherever InfraNest suggests it.
3. Review the settings on the **Monitor what was added** step.
4. Click **Save automation**.

## Choose how and where it checks
1. On the **Monitor what was added** step, set **Check interval** to control how often new monitors check in.
2. Set **Check from** to choose the checking location:
   - **Where new monitors usually run** keeps your account's usual default location.
   - **Nearest to the address** automatically picks the location closest to whatever is being checked.
3. Click **Save automation** to apply your choices.

## Review what it has done
1. Before switching it on, check the suggested automations section — the recipe shows how many things added in the last 30 days still have no monitor.
2. After it's running, open the rule's run history to see each run.
3. Each run entry explains what was created or connected, or the reason something was left alone.

> [!NOTE]
> This automation only covers things added after you turn it on. Anything added earlier isn't touched — use the suggestions on the monitoring page to add monitors for those.

## Tips
- If you already have separate automations for monitoring new servers or new websites, this one covers both and more — keep just one running so each new item is only handled once.

## Troubleshooting
- **Nothing was created for a new domain or server.** Check the run history — it explains why. Common reasons include a parked domain, a server with no public address, or a status page component with a name that doesn't match a checkable address.
- **A monitor wasn't created because of your plan.** When your plan has no room for another monitor, the run says so and nothing is created. If a location or check interval isn't included in your plan, the run shows what was used instead.
- **The automation isn't running at all.** Remember it's opt-in — it's never switched on automatically. Open **Automations** and confirm it's saved and enabled.