I agree, we should be restricting #page to alerts that page folks, not sure of an alternative tag though (or remove the tag altogether for now) cc @ayounsi

@CDanis set it up, there is a Icinga check that pulls the LibreNMS api and should page where #page is present. But should not page for management routers.
@fgiunchedi Maybe that's something now doable directly through Alert Manager instead? (and we can stop using the #page tag?)

For the record, the #page alerts from management routers should be fixed with T278289

In T281055#7032875, @ayounsi wrote:

@CDanis set it up, there is a Icinga check that pulls the LibreNMS api and should page where # page is present. But should not page for management routers.
@fgiunchedi Maybe that's something now doable directly through Alert Manager instead? (and we can stop using the # page tag?)

Yes I think at this point we should page through AM for librenms alerts and ditch the icinga check, now tracked in T281095

Moving to AM sounds good to me. But if needed, in the interim we could change the magic string we use in check_librenms to something else instead of hash page, which I chose for simplicity but has maybe just caused more confusion.

All we'd have to do is to change the --escalation-pattern flag value and also change the names of the alert rules in LibreNMS.

In T281055#7034863, @CDanis wrote:

Moving to AM sounds good to me. But if needed, in the interim we could change the magic string we use in check_librenms to something else instead of hash page, which I chose for simplicity but has maybe just caused more confusion.

All we'd have to do is to change the --escalation-pattern flag value and also change the names of the alert rules in LibreNMS.

SGTM to change the hashtag and pattern in the meantime. I won't have time to look into it shortly but happy to review patches

Mentioned in SAL (#wikimedia-cloud) [2024-03-12T19:59:05Z] <wmbot~bd808@tools-sgebastion-11> Update to a3bef6e (T128868, T140881, T90339, T281055, T180293)