Add a monitor

Monitor your websites, APIs, certificates, DNS records, and more, so you're the first to know when something breaks. This guide is for anyone setting up or managing checks in InfraNest.

#Overview

• Monitors run automated checks on a schedule and alert you when something goes wrong.
• You can monitor many types of targets: websites, APIs, certificates, DNS records, servers, and more.
• Each monitor can be fine-tuned with its own interval, alert thresholds, regions, and alert destinations.

#Add a monitor

1. Go to Monitors and select Add monitor.
2. Choose the type of check you want (see the list of monitor types, such as HTTP / website monitoring, Ping monitor, DNS monitoring, and others) and enter its target — for example a URL.

3. Set the Check interval and any type-specific settings, like the expected content or DNS value.
4. Fine-tune if you want:
   • Slow response time alert — mark the check as degraded when it's up but slower than the threshold you set.
   • Failed checks before alerting — how many checks in a row must fail before you're alerted. Higher values ignore brief blips.
   • Probe regions and IP version (Prefer IPv4 (recommended), Prefer IPv6, IPv4 only, or IPv6 only).
   • Notification policy — where alerts for this check go.
5. Use Test connection to check your settings, then select Save.

TipFor Ping monitor, Port monitoring, and DNS monitoring checks, the target is a hostname, like example.com. If you paste a full web address such as https://example.com/page, only example.com is kept.

TipThe Create monitor form suggests a Monitor name from the URL as you type it. Change it any time; once you do, it stops following the URL.

#Manage a check

1. Go to Monitors and select the check you want to review.
2. Open the monitor to see Latest incidents, Latest checks, and its history.
3. Use Enable or Disable to turn the check on or off.
4. Use Silence alerts and choose Silence for a set duration if you expect downtime or don't want alerts right now.
5. Set a Dependencies link to another monitor using Add parent or Add child if this check relies on something else.

#Troubleshooting

• If Test connection fails, double-check the target address and any type-specific settings, like Expected status codes or Keyword to find in response.
• If you're not getting alerted, check Notification policy and make sure the right destinations are chosen under Choose destinations.
• If a monitor looks stuck, use Refresh to pull the latest results, or Retry a failed check.