Hello, for some reason I can’t wrap my head around what is the difference between “fired alert” and just “alert”?
Sometimes they behave same way and sometimes not?
Thank you.
Not sure where your ‘fired’ terminology comes from - do you mean when an alert is triggered (some condition met, such as ping failed), versus when it sends a notification via whatever transports you have configured (when Delay, Interval etc. conditions are met)?
When creating a dashboard and adding a alert widget, there is option to filter “show only fired alerts”
I’ve never noticed that before. It looks to have been around for 7+ years and was intended to relate to delayed notifications - there is a good explanation here: Added feature to filter delayed alerts on widget by SitWatchCloudRise · Pull Request #8704 · librenms/librenms · GitHub
I don’t have any fresh alert to test on right now, but if I put two widgets side-by-side with my current alerts, the ones I have with ‘Mute Alerts’ set go missing from the fired filtered one.
So this is saying that if an alert has triggered, but hasn’t sent a notification due to it having not yet reached its delay conditions, or because it is muted - then it’s not considered fired (notified) yet, and maybe at this point you could consider it not real depending on what is normal for your setup and devices.
On a bad comms link that chews packets and miss the odd polling cycle or ping - with a sane delay of 300, it would show as an alert, but not notify unless it was still in the same failed state on the next check after 300 seconds. Filtering for fired would only show it after it has finished the delay, is unmuted, and reached the point where it can send a notification - so you’re potentially tuning out some noise.
Someone else with more knowledge can educate us both hopefully!
Edit: and it’s most certainly not a stupid question, it’s taught me things that I didn’t even know I didn’t know 
Thank you, that seems to make sense 