Comment 1 for bug 1551217

This is actually two different issues.

These alert have likely never been held back from your alert profile, because withholding of SMS/e-mail/jabber/etc alerts takes place in specific eventengine plugins. 3rd party alerts, like those from Xymon, do not have specific eventengine plugins, and are only processed by the generic eventengine handler. This handler doesn't verify maintenance status at all, and has _never_ done this (in the Python incarnation, which I believe has been around since NAV 3.6 or so). We should probably do this in the generic handler too, though.

When it comes to the status page, the problem is actually that the Xymon alerts have a subject ID that corresponds to Xymon's internal service number. NAV tries to check the maintenance status for this subject, but since it doesn't have any internal knowledge of this Xymon-specific ID, it finds no such thing. However, it should probably fall back to just checking the maintenance status of the netbox itself, if the Xymon alert is associated with a netbox registered in NAV.

In the latter case, I believe the only difference you'll find from before is that Xymon alerts weren't displayed at all in the status page in NAV versions prior to 4.2 (november 2014).