跳至主要内容
版本:0.4 · 現行版

綜合檢查模組的檢查

參考審閱日期:2026年10月11日
適用於:Excubius 0.4角色: 操作員, 編輯者, 實體管理員
方案Free · Pro · Enterprise部署自行託管

synthetics 模組有 9 項檢查。主動檢查,演練過去出現過故障的路徑:由 VNet 內的採集器(私人位置)執行,亦可選擇使用 New Relic Synthetics。

本頁面在建置文件時由產品的檢查目錄產生,因此規則、間隔及預設嚴重程度一律與你正在閱讀的版本相符。閾值是預設值;實體和資源可以覆蓋這些閾值。

檢查間隔預設嚴重性規則
synthetics.http_endpoint
HTTP endpoint availability and response time
60scriticalwarning > 2000 milliseconds · 5m / critical > 10000 milliseconds · 2m
synthetics.tls_certificate
TLS certificate validity
3600swarningwarning < 30 days / critical < 7 days
synthetics.dns_resolve
DNS resolution of the endpoint host
300scriticalwarning > 500 milliseconds / critical > 2000 milliseconds
synthetics.ag_listener_resolve
Listener name resolves from the collector
120scriticalwarning > 500 milliseconds / critical > 2000 milliseconds
synthetics.domain_auth
Domain authentication round trip (AADDS)
300scriticalok = true
synthetics.app_to_sql
Application-to-SQL round trip through the listener
60scriticalwarning > 500 milliseconds / critical > 5000 milliseconds
synthetics.ssrs_report_render
SSRS report render test
900scriticalwarning > 15000 milliseconds / critical > 60000 milliseconds
synthetics.ssrs_execution_log
SSRS execution log failures
600swarningwarning >= 1 count / critical >= 5 count
synthetics.platform_heartbeat
Platform dead-man heartbeat
60scriticalcritical > 5

檢查​

synthetics.http_endpoint

HTTP endpoint availability and response time

量度
response_ms (milliseconds) · 每 60s · http
規則
warning > 2000 milliseconds · 5m / critical > 10000 milliseconds · 2m · 預設嚴重性: critical
措施
—
基準
Status or content mismatch is critical regardless of latency.

synthetics.tls_certificate

TLS certificate validity

量度
days_to_expiry (days) · 每 3600s · http
規則
warning < 30 days / critical < 7 days · 預設嚴重性: warning
措施
—
基準
Chain validity, hostname match and minimum TLS version are hard failures.

synthetics.dns_resolve

DNS resolution of the endpoint host

量度
resolve_ms (milliseconds) · 每 300s · dns
規則
warning > 500 milliseconds / critical > 2000 milliseconds · 預設嚴重性: critical
措施
—
基準
Resolution failure (or an unexpected address) is critical; slow resolvers are a warning.

synthetics.ag_listener_resolve

Listener name resolves from the collector

量度
resolve_ms (milliseconds) · 每 120s · dns
規則
warning > 500 milliseconds / critical > 2000 milliseconds · 預設嚴重性: critical
措施
Check the listener's DNS record (RegisterAllProvidersIP, TTL) and the cluster network name resource.
基準
Applications reach the group through this name; a listener that does not resolve is an outage even when every replica is healthy.

synthetics.domain_auth

Domain authentication round trip (AADDS)

量度
latency_ms (milliseconds) · 每 300s · winrm
規則
ok = true · 預設嚴重性: critical
措施
—
基準
This is the check that would have caught the authentication outage. Critical on first failure.

synthetics.app_to_sql

Application-to-SQL round trip through the listener

量度
latency_ms (milliseconds) · 每 60s · tsql
規則
warning > 500 milliseconds / critical > 5000 milliseconds · 預設嚴重性: critical
措施
—
基準
Connects to the listener name, not a node, so DNS, cluster IP and primary role are all exercised.

synthetics.ssrs_report_render

SSRS report render test

量度
response_ms (milliseconds) · 每 900s · http
規則
warning > 15000 milliseconds / critical > 60000 milliseconds · 預設嚴重性: critical
措施
—
基準
HTTP status other than the expected one is critical.

synthetics.ssrs_execution_log

SSRS execution log failures

量度
failed_executions (count) · 每 600s · tsql
規則
warning >= 1 count / critical >= 5 count · 預設嚴重性: warning
措施
—
基準
Subscriptions that fail silently show up here; group by report path.

synthetics.platform_heartbeat

Platform dead-man heartbeat

量度
heartbeat · 每 60s · http
規則
critical > 5 · 預設嚴重性: critical
措施
—
基準
An external watcher (healthchecks-style, e.g. Uptime Kuma or Azure Monitor availability test) must alert if the platform stops pinging.