might also be me

been waiting for few minutes tho, the alert is being matched in the capture but is not displayed.. yet

it would be great to have "clear alerts" aswell option 😄 or 'send recovery alert notification even if alert is active' https://cdn.discordapp.com/attachments/327529583601647617/1558098223862648832/image.png?ex=6aca338c&is=6ac8e20c&hm=e15c27bca16c0cfcc9584dfda785017cba9d12612dcf840162ba2c3ead26151f&

so active alerts are cleared -> notification is sent out with cleared -> tickets close

maybe the ack alert should be used for that... but we don't use that, cause some automation is using that, they log into librems and "ack" the alert automatically and put the ticket number into the ack note, it's a nice way to trace the ticket number directly, but maybe not intended use

I have a ticket to "clear" the alert automatically myself, by putting in description notes #Unmanaged:{maintenance - blahblahreason} so the alert is simply not matching devices with that in the description, but it's annoying to have two ways to put inthe scheduled maintenance

#Unmanaged:{} this will be ok, so people can add the 'maintenance' and the alert will be cleared and tickets close, issue with this you have to do it manually per device

but I dunno, I got mute maintenance mode active on my device, but I been waiting for a while now, I think it's not getting matched

I looked at that option to see the alerts still, so we don't blind ourselves when we are working on changes

gonna see if I can make it "clear" the alert, that would at least be one nice thing 😄

I can't replicate not being able to see the fault/alert. I'm guessing your rule isn't matching or you have it assigned to groups/devices that don't match

mute option is not also doing the "clear" alert, even if it blocks the alert somehow from showing

You can't clear alerts if the rule is still matching, they will just come back

I do get the alert if I remove the maintenance

if I do capture, while the maintenance mode is active or not, the alert is matching

if I add the condition I described above with "maintenance" in description ( or purpose field ), I don't get alert match in capture

waiting to see if the alert itself is then removed as the condition for the alert should not be met with maintenance in the description, but device is under 'mute mainteance mode'

it's as if the 'mute' is stopping the alert from being run, it's not clearing under maintenance mode aswell, even if I set that condition correctly

gonna see now if it's cleared if I remove the mute maintenance mode

could it somehow be related to that I'm planning the scheduled maintenance using a group? but then the alert is also only matching other specific groups? So the device is multiple groups

so we only have the alert match devices in group X Y Z, based on priority or SLA. so device is in those groups, the alert is then matching those groups. but then we have another group for the 'site', and I plan the mainteance using that group

I'm really not following you but if you're saying the maintenance is in one group but the rule is for another group then the maintenance won't match

the device is in both groups. the alert is matching groups that is covering many devices depending on severity, we have different rules based on how severe the device is, but I'm maybe not making myself clear enough

I will add the alert to match the site group, see if I get the 'bug' to go away

I've tested maintenance alerts and they don't affect alerts/faults showing in the webui for me.

Alerts are also suppressed when skip/mute alerts is set

I've just changed from Legacy Unrestricted (using Cron) to the Displatcher Service - does the Poller Cluster Health replace the Standard Poller? https://cdn.discordapp.com/attachments/327529583601647617/1558164260637638756/image.png?ex=6aca710d&is=6ac91f8d&hm=71440cc105b19631bedc60652a21739bfd5d99755907f6ac6753a795647e57ec&

I can see in the log devices are definitely being polled by the dispatcher, but I can only guess the cluster health is a new replacement when you swap over?

Data does seem to be coming into RRD files etc so I can only assume all is ok?

do I just hit delete on the old standard poller maybe?