Hi everyone,
I couldn’t find exactly what I was looking for in the existing topics.
I’m currently working with a LibreNMS instance that monitors around 1,500 devices. In the long term, with 8 pollers and 2 RRDs, we expect to reach about 15,000 devices. Our network changes frequently and generates a lot of alerts. For example, some ports go “down” when we modify their configuration. This triggers an alert in the corresponding port notification (which is expected), but the issue is that the alert remains visible in the notifications window even after it has been acknowledged.
Is there a way, directly from the WEBUI, to add a checkbox and a menu option to acknowledge alerts in bulk, or to delete certain alerts from the database, without having to access the database backend directly?
Thank you,
Guillaume
Bonjour Guillaume,
In LibreNMS logic, an alert is generated from a state. Basically an SQL that triggers the alert. Removing an alert does not make sense, cause as long as the condition is there, it will come back next poll.
You need to define your alerts in a way that only significant alerts are generated. Not always easy.
I personnaly use the description of ports/interfaces to “tag” ports that are backbone, customer, accesspoints, etc etc. And that allows better rules and better alerting.
Hello, thank you for your feedback. I understand what you mean, but my alarms are configured more or less correctly. However, changes in the network topology cause some alarms to appear and never clear, so they remain in the alarm list. Having the ability to acknowledge alarms in bulk would already be a great improvement!
Best regards,
Guillaume
Hello, I’m coming back to this topic. Since it isn’t possible to delete alarms directly from the page, it should at least be possible to perform multi-selection with checkboxes (individual selection or “select all”) to acknowledge all alarms at once (or filtred alarm).
In my case (I understand this may not apply to everyone), that would be a huge help. Even when working directly on the database, we can’t retrieve the alarm number from the interface, which makes it difficult to delete alarms from the database.
Or, if you have a simple solution to suggest, I’m open to it.
Thank you.
I’m closing this topic.
Alarms don’t work in that way, deleting them will just mean they come back the next poll as has been explained. You need to either adjust your rules so they don’t trigger under the conditions you don’t want them to or use things like Ack or maintenance to suppress them. You can even not assign an operation to a rule so that it doesn’t send any notifications out.