Monitored Resources

# Introduction

Monitored Resources are the core of Emercom's uptime monitoring system. They continuously check your services and alert you the moment something goes wrong.

# Quick Start

Get your first monitor up and running in under 2 minutes:

# Resource Types

Emercom supports three types of monitored resources, each designed for different use cases:

# HTTP Monitoring

HTTP monitoring is the most comprehensive option, perfect for websites, APIs, and web applications. It checks not just availability, but also response codes, SSL certificates, and content.

Configuration Options

Check Statuses

Example Configuration

Name: Production API
URL: https://api.myapp.com/v1/health
Check Interval: 1 minute
Expected Status: 200
Response Time Threshold: 2000ms
SSL Check: Enabled
SSL Warning: 14 days before expiry
Body Contains: "status":"ok"

# Port Monitoring

Port monitoring checks if a specific TCP or UDP port is open and accepting connections. Ideal for databases, mail servers, game servers, and any service running on a specific port.

Configuration Options

Common Ports

# ICMP Monitoring

ICMP (ping) monitoring checks basic host reachability. It's the simplest form of monitoring and is great for checking if a server or network device is online.

Configuration Options

Understanding Results

Packets: 4 sent, 4 received, 0% packet loss
Round-trip time:
  Min: 12ms
  Avg: 15ms
  Max: 23ms

Status: SUCCESS (100% success rate, 15ms avg RTT)

# Check Intervals

Choose how frequently Emercom checks your resources. Shorter intervals mean faster detection but use more credits.

# SSL Certificate Monitoring

Never let an SSL certificate expire unexpectedly again. Emercom monitors your certificates and warns you before they expire.

What Gets Monitored

• Certificate Validity - Is the certificate trusted and not revoked?
• Expiration Date - When does the certificate expire?
• Certificate Chain - Is the full chain valid?

Warning Thresholds

Configure when you want to be warned about expiring certificates:

SSL Diagnostics

When SSL issues are detected, Emercom automatically captures the full certificate chain for analysis. You can download the .pem file from the diagnostic results.

# Notification Channels

Get alerted through multiple channels to ensure you never miss a critical notification.

# Escalation Rules

Escalation ensures critical alerts reach someone, even if the first contact doesn't respond. If no confirmation is received, alerts automatically escalate to the next notification method.

How Escalation Works

Escalation Settings

Recovery Notifications

When a resource recovers, recovery notifications are sent to all methods that were used during escalation. If alerts were sent via email and SMS, recovery notifications go to both.

# Confirmation System

The confirmation system ensures someone has acknowledged the alert before stopping escalation.

How to Confirm

# Automatic Diagnostics

When a resource goes DOWN, Emercom automatically runs a suite of diagnostic commands to help you identify the root cause quickly.

When Do Diagnostics Run?

• Resource fails on more than 2 monitoring servers
• At least 10 minutes since last diagnostic run (cooldown)
• Or manually triggered via "Run Diagnostics" button

# Manual Diagnostics

You can trigger diagnostics at any time, even if the resource is currently up.

Test Now vs. Run Diagnostics

# Diagnostic Commands

Different resource types run different diagnostic commands based on what's most useful for troubleshooting.

HTTP Diagnostics

Port & ICMP Diagnostics

# Sharing Diagnostic Results

Share diagnostic results with team members, support, or vendors without giving them access to your Emercom account.

Creating a Share Link

1. Open the check result with diagnostics
2. Click the "Share" button
3. Choose an expiration time (hours, days, months, or never)
4. Copy the unique link

# 365-Day Activity Heatmap

Get a bird's-eye view of your resource's health over the past year with the activity heatmap.

Understanding the Colors

• No checks performed that day
• 1-2 checks
• 3-5 checks
• 6-10 checks
• 11+ checks

Hover over any day to see the exact number of checks and success rate.

# Response Time Charts

Track response time trends over the last 24 hours to identify performance issues before they become outages.

The spike at 4 hours ago would indicate a temporary performance issue worth investigating.

# Filtering Results

Use powerful filters to find exactly the check results you're looking for.

Available Filters

# Monitoring Incidents

When a resource goes down, Emercom creates a monitoring incident that tracks the outage from start to finish.

Incident Lifecycle

# Multi-Server Monitoring

Every check runs from multiple monitoring servers around the world. This provides redundancy and helps identify regional issues.

Our Global Network

Emercom monitors from 12 locations across North America, Europe, and Asia-Pacific.

Failure Detection Logic

To reduce false positives, a resource is only marked as DOWN when:

// Resource is DOWN when:
consecutiveFailures > 2 servers

// This means:
- 1 server fails → Still UP (might be network issue)
- 2 servers fail → Still UP (could be regional)
- 3+ servers fail → DOWN (likely real outage)

# IP Protocol Selection

Choose which IP protocol Emercom uses when resolving hostnames.

# Credit System

Monitoring checks consume credits from your organization's balance.

Credit Usage

• 1 credit per check, per resource
• Credits are deducted when the check runs
• Failed checks (insufficient credits) are skipped but logged

Estimating Usage

// Credits per month = checks per day × 30

1-minute interval:  1,440 checks/day × 30 = 43,200 credits/month
5-minute interval:    288 checks/day × 30 =  8,640 credits/month
10-minute interval:   144 checks/day × 30 =  4,320 credits/month

# Next Steps