Features in v1.6.7

Current status, retained evidence, and focused troubleshooting

Lantern monitors user-selected endpoints from one Windows machine. Its web interface separates everyday status from historical review, diagnostics, discovery, and maintenance.

Dashboard

Operate hosts and groups from one live view

Tile and list views show state, latest latency, timeframe packet loss and availability, last success, and recent online/offline/degraded events.

  • Searchable multi-select group and host filters
  • Retained and custom timeframes
  • Host/group create, edit, delete, and drag ordering
  • Rapid successive host entry while reusable choices remain selected
Deleting a group moves its hosts to Ungrouped; it does not delete them.

Network Overview

Compare retained history across hosts

Per-host latency and packet-loss graphs use the selected timeframe and resolution. Filter by groups or hosts, expand a graph, and save host order when filters are clear.

Auto resolution keeps ordinary requests bounded; custom ranges can request resolutions from raw 5-second data through one-day buckets. Older history has lower resolution after retention rollup.

Interpret loss, event overlays, and gaps alongside latency.

Advanced Diagnostics

Collect context around confirmed failures

Manual and automatic runs collect target ICMP evidence, route context, gateway reachability, direct DNS-server checks, and a bounded traceroute.

  • Gateway and DNS Server infrastructure roles; no separate Internet role
  • Diagnostics enabled per target or group
  • Automatic runs on confirmed outage and confirmed recovery, not degradation alone
  • Complete, partial, failed, or cancelled saved records
Infrastructure roles and target enablement are separate.
Manual and automatic target controls.
Saved component evidence and run status.

IP Scanner

Find responding IPv4 devices before monitoring them

Scan a CIDR or inclusive start/end range of at most 1,024 accepted addresses. Direct-subnet ARP and ICMP provide discovery; hostname, MAC address, and bundled offline vendor lookup are best effort.

Live progress and cancellation keep the scan visible. Add selected results to monitoring; existing or duplicate targets are skipped, and new hosts are enabled, Ungrouped, and tagged scanner.

CIDR or explicit range, bounded to 1,024 addresses.
A missing result does not prove that an address is unused.

Outage History

Review active and recovered outages

After repeated failures confirm Offline, Lantern records an outage from the first failure. Confirmed recovery closes it. The page follows Dashboard group and host order, summarizes counts and latest incidents, and expands each host into start, recovery, duration, and ongoing/recovered state.

Choose 1 hour, 6 hours, 24 hours, 7 days, 30 days, or All; the saved range controls the on-page hierarchy. CSV export is separate: it exports the newest stored outages, up to 5,000, and is not narrowed by the selected page range. Retention selectors do not prune outages.

Degraded events remain distinct from outages.

Application Health

Check whether Lantern itself is keeping up

The health view refreshes application status, version, process uptime, total SQLite storage, configured/enabled hosts, active monitor tasks, latest monitoring cycle, and up to 20 recent monitoring-error messages.

Use active-task count and cycle recency as operational evidence; v1.6.7 does not calculate a separate stale-cycle alarm or query Windows Service Control Manager status.

Cycle freshness helps distinguish monitor trouble from a host outage.

Settings, retention, and data

Control history depth and maintain local storage

Separate selectors retain raw samples, one-minute history, one-hour history, and finished diagnostic runs. Storage statistics show physical files, reusable space, and relevant row counts.

Clear Monitoring History preserves active incidents; Clear Diagnostic History preserves active runs; Clear All Data performs both. Hosts, groups, roles, settings, monitoring errors, and active work survive. Optimize Database compacts and integrity-checks SQLite without deleting data.

The packaged page can request service Stop or Restart. A stopped service no longer monitors and cannot serve the local UI.

Four independent retention categories.
Physical and reusable storage information.
Confirmed destructive actions and optimization.
Runtime paths, version, and service controls.

Operate it confidently

Read the full v1.6.7 guide

See exact defaults, state transitions, diagnostic interpretation, scanner safeguards, destructive-action scope, and troubleshooting steps.