I'm running cachet-monitor on two different hosts in different geographical locations and if they both detect a monitor down condition, subscribers receive two notifications. The "Updates Component to Major Outage if already in Partial Outage (works with distributed monitors)" is not working the way I would expect it to (doesn't switch to major outage), so it is possible I do not have it set up properly. Here is my monitor config:
{ "api": { "url": "https://REDACTED/api/v1", "token": "REDACTED", "insecure": false }, "date_format": "Mon Jan _2 15:04:05 MST 2006", "monitors": [ { "name": "Website", "target": "https://REDACTED", "strict": true, "method": "GET", "component_id": 1, "interval": 5, "timeout": 5, "threshold": 90, "expected_body": ".*Website.*", "template": { "investigating": { "subject": "{{ .Monitor.Name }}", "message": "{{ .Monitor.Name }} automated test has failed at {{ .now }}\n\nIT Staff have been alerted." }, "fixed": { "subject": "{{ .Monitor.Name }} incident has been resolved." } } } ] }
I'm running cachet-monitor on two different hosts in different geographical locations and if they both detect a monitor down condition, subscribers receive two notifications. The "Updates Component to Major Outage if already in Partial Outage (works with distributed monitors)" is not working the way I would expect it to (doesn't switch to major outage), so it is possible I do not have it set up properly. Here is my monitor config:
{ "api": { "url": "https://REDACTED/api/v1", "token": "REDACTED", "insecure": false }, "date_format": "Mon Jan _2 15:04:05 MST 2006", "monitors": [ { "name": "Website", "target": "https://REDACTED", "strict": true, "method": "GET", "component_id": 1, "interval": 5, "timeout": 5, "threshold": 90, "expected_body": ".*Website.*", "template": { "investigating": { "subject": "{{ .Monitor.Name }}", "message": "{{ .Monitor.Name }} automated test has failed at {{ .now }}\n\nIT Staff have been alerted." }, "fixed": { "subject": "{{ .Monitor.Name }} incident has been resolved." } } } ] }