From 276e6044fd179adf5a51390c0a92b50129196b5a Mon Sep 17 00:00:00 2001 From: Fuwn Date: Mon, 19 Jan 2026 19:53:36 -0800 Subject: fix: Remove duplicate monitor name validation across groups Previously, monitors with the same name in different groups would fail validation. This restriction has been removed to allow duplicate names across groups, restoring the original behavior. Note: Monitors with duplicate names will share the same data in the database since MonitorName is used as the identifier. A future enhancement could use group+name as a composite key. --- config.example.yaml | 2 ++ 1 file changed, 2 insertions(+) (limited to 'config.example.yaml') diff --git a/config.example.yaml b/config.example.yaml index 383c0b4..d751ac5 100644 --- a/config.example.yaml +++ b/config.example.yaml @@ -195,6 +195,8 @@ incidents: # # Common fields for all monitor types: # name: string (required) - Display name for the monitor +# NOTE: Duplicate names across groups are allowed but will share +# the same monitoring data in the database # type: string (required) - Monitor type: http, https, tcp, gemini, icmp, dns, or graphql # target: string (required) - URL, host:port, IP address, or domain to monitor # interval: duration - Check interval (default: 30s, or group default) -- cgit v1.2.3