Complete Probes and History

简体中文 | English

Three Probe Triggers

A complete probe can start in three ways:

• Probe now runs only the public IPs selected for this invocation and does not change recurring enablement.
• Recurring schedule runs all enabled public IPs according to the node's Cron expression and timezone.
• Probe newly discovered public IPs is a node setting that probes only a new address found on an established discovery path.

Probe-now from the node list opens a selector containing current public IPs. The immediate action on a public-IP row submits that IP directly without a second selection. An address can be probed once even when recurring probes are disabled for it.

The recurring schedule uses a six-field Cron expression including seconds and an explicit IANA timezone. It defaults to midnight, with the administrator's browser timezone recorded by the enrollment key as the node default. When the expression or timezone changes, the page shows the next run in that timezone. IPChronicle imposes no additional frequency limit.

Task State

An immediate task can be created only for an online node and may wait up to two minutes for the Agent to receive it. Each node has one immediate-task slot and no backlog. Agent updates and complete probes compete for that slot. The page shows whether the Agent received the task and each public-IP execution's progress and terminal state.

Scheduled runs missed during downtime are not caught up. A new schedule occurrence is skipped while another probe is already running.

Probe Results

The Agent uses the built-in Go probe. HTTP, HTTPS, and SMTP checks use the direct or proxy path associated with the target public IP. DNS and DNSBL checks use the node resolver.

Failure of one third-party provider leaves only that provider's fields empty; it does not fabricate values or fail unrelated checks. JSON null means that no data is available and is not a format error. If a known field changes to an incompatible type, the interface shows an empty value while preserving the raw report and format diagnostics.

The result page preserves each provider's own meaning for location, type, risk factors, risk score, media access, and mail connectivity. Known field names and values are presented in human-readable language; unknown values remain visible unchanged. A report can be downloaded as PNG or copied directly as PNG.

History and Comparison

The History page filters by node, public IP, time, outcome, trigger, format state, and change state. Snapshot comparison selects two results for the same public IP. It initially shows the earliest and latest snapshots and allows the start and end times to change. Starred snapshots are exempt from retention cleanup.

Address history records only state changes such as set entry, set exit, failure, and recovery. It does not retain every unchanged check.

Retention Policies

Under Settings > History and storage, select:

• indefinite retention;
• age retention from 1 through 36,500 days; or
• logical-size retention from 1 MiB through 1 TiB.

Cleanup runs when the policy changes, on manual request, and every six hours. Current state, starred snapshots, active notification deliveries, and required comparison baselines are protected, so physical storage can exceed a logical size budget.

While the Center is unavailable, an Agent retains at most 30 pending complete results per public IP. Address events are bounded per hidden discovery path. Eviction creates an explicit history gap. Upload retries transmit saved data and never rerun a probe.