Telenegar Uptime Monitoring Tool

The Telenegar Uptime Monitoring Tool provides automated, scheduled health checks for websites, web applications, and network services. It continuously tracks service availability, response times, and downtime across multi-geographical probe locations.

Unlike one-time diagnostic queries, Uptime Monitoring allows administrators to set scheduled monitoring jobs (HTTP or TCP) to detect outages early, measure performance trends over time, and minimize downtime for mission-critical infrastructure.

Target Types & Configuration Options

When creating a new monitor (+ New Monitor), you can select between two fundamental check types:

1. Website (HTTP / HTTPS) Monitoring

Performs full HTTP/HTTPS web requests and validates HTTP status codes returned by the web server.

Parameter	Description	Example / Values
HOST	Domain name or IP address of the target server.	e.g., `catc.ac.ir`, `telenegar.ir`
SCHEME	Protocol scheme used to send the request.	Options: `http`, `https`
PORT	Target network port (defaults based on scheme).	e.g., `443` (HTTPS) or `80` (HTTP)
PATH (OPTIONAL)	Specific URL endpoint or healthcheck path to query.	e.g., `/health`, `/api/status`

2. Raw Port (TCP) Monitoring

Tests whether a specific network port accepts TCP connections (`SYN/ACK`) without sending HTTP payloads. Ideal for non-web services such as SSH, databases, and mail servers.

Parameter	Description	Example / Values
IPV4 ADDRESS	Target IPv4 address of the service host.	e.g., `203.0.113.10`
PORT TO CHECK	Target TCP port number to monitor.	e.g., `22` (SSH), `3306` (MySQL), `25` (SMTP)

Monitoring Schedule & Probe Settings

Setting	Description	Options / Behavior
PROBE(S)	Multi-select remote probes to conduct checks from different geographical locations.	Examples: `Tehran, Iran — Atrin (ATR01)`, `Falkenstein, Germany — Hetzner (HTZ01)`. Note: Hold Ctrl (Cmd on Mac) to select multiple probes.
INTERVAL	Frequency of automated monitoring checks and credit cost per hour.	Options: • `1 min (8 Cr/hr)` • `5 min (1 Cr/hr)`
START / STOP	Schedule exact date and time windows for active monitoring.	Format: `MM/DD/YYYY, HH:MM AM/PM`
Down Alert Logic	Reduces false positives by verifying failure consensus.	A “down” alert fires only when all selected probes simultaneously report that the target is unreachable.

Metrics & Dashboard Analytics

The Uptime Monitoring dashboard and detailed analytics view (View Curves) provide key performance indicators (KPIs) and historical trends:

Uptime Percentage: Overall service uptime recorded over selectable windows (24h, 7 days, 30 days).
Average Response Time: Mean latency in milliseconds (`ms`) across all active probes.
Total Checks: Total number of completed probe execution runs within the selected timeframe.
Multi-Probe Response Graph: Visual breakdown of response time curves comparing domestic and international vantage points (e.g., `ATR01` vs `HTZ01`).
Status & Downtime Timeline: Visual event log tracking status changes, uptime periods, and downtime incidents.
Monthly History Table: Periodical audit breakdown tracking execution period, uptime percentage, average response time, check counts, and recorded downtime.

How to Set Up an Uptime Monitor

# **Navigate to Uptime Monitoring:** Open the tool and click the **+ New Monitor** button.
# **Select Target Type:** Choose **Website (HTTP)** for web services or **Raw Port (TCP)** for port-level monitoring.
# **Enter Service Details:** Input host/IP address, protocol, port, and optional path.
# **Select Probes & Check Interval:** Choose one or more probe locations (e.g., Tehran and Germany) and select either a 1-minute or 5-minute interval.
# **Define Schedule:** Set the **START** timestamp and optional **STOP** timestamp.
# **Activate Monitor:** Click **Set Up Monitoring** to initiate automated testing.

Key Use Cases & Applications

1. SLA & High-Availability Verification

Track Service Level Agreement (SLA) metrics and overall uptime percentages for public-facing web applications and enterprise portals.

2. Synthetic Endpoint Monitoring

Monitor dedicated API health endpoints (e.g., `/health`) to verify that underlying databases, caches, and dependent microservices are operating correctly beyond basic web server availability.

3. Non-Web Service Uptime Tracking

Ensure continuous uptime for core backend infrastructure—including mail routing servers (`25`), database instances (`3306`, `5432`), and administrative jump hosts (`22`).

Telenegar Knowledge Base

Table of Contents