Do you mean in so much as just setting an alert checker to be a severity, so you can use that bit of meta data elsewhere?

Like I mentioned earlier, the reason I’d not implemented that already is because that always seemed little simplistic to me, like there was a gotcha scenario just waiting to appear.

Adam.

On 6 May 2020, at 22:08, Ryan, Spencer J. via observium <observium@observium.org> wrote:

I agree being able to set the priority would be good. Many downstream notification systems can have their own routing logic based on severity, time of day, etc. 
 
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Mark Sanchez via observium
Sent: Wednesday, May 6, 2020 2:28 PM
To: Observium
Cc: Mark Sanchez
Subject: Re: [Observium] Reoccuring Scheduled Maintenance
 
CAUTION EXTERNAL EMAIL: DO NOT open attachments or click links from unknown or unexpected emails.
 
We have setup our ticket platform (ServiceNow) to use the severity sent over, which has been critical for everything.
 
I like the idea of having it in the UI as a configurable field, which makes scaling this better/easier.
 
If this is something you plan to do, please let me know an ETA - it might save from bandaid-ing the way you mentioned.
 
Thanks Adam.
 
Kind Regards, 
Mark Sanchez


On May 6, 2020, at 2:21 PM, Adam Armstrong via observium <observium@observium.org> wrote:

If I was to add severities, it’d probably be in the form of multiple tests so an individual checker can return different severity levels.
 
I’m not sure I understand the need otherwise, except as a manual field you can set in an alert checker and have that passed through in an alert. This can easily be done by just putting some text in the alert checker description.

 

Confidentiality Notice

This communication constitutes an electronic communication within the meaning of the Electronic Communications Privacy Act, 18 U.S.C. Section 2510, and its disclosure is strictly limited to the recipient intended by the sender of this message. This transmission and any attachments may contain confidential information and work product(s). If you are not the intended recipient, any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. Please contact deepwatch immediately by return e-mail or call (855) 303-3033 and destroy the original transmission and its attachments without reading or saving in any manner.

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium