So, after the upgrade to 2026.2.1 lots of folks were mentioning that they were missing alerts, they were just gone, and they were left with a handful of alerts if any. At that time I figured out it was that the "CreatedBy" field in the database was NULL, and that setting it to any valid account would bring them back.
About a week ago, I upgraded to 2026.2.3, and someone noticed that some of our alerts were gone, including our "Node Down" alert. Not good. I figured it was the same reason, so I went into the database, and alerts that were missing had that field set. So I looked a little bit further. Turns out all of the alerts missing (over 200 in our case) had the "Hidden" field set. Most of those alerts were disabled, but for the few that still had the Enabled field set, they weren't working either. Simply clearing this "Hidden" flag restored the alert to being seen in the Alert Manager, and those that needed to trigger did. So, simple fix.
With the 2026.2.1 problem, just running the config wizard would make it happen again, it would set some of the "CreatedBy" fields to NULL and you'd have to start over again. Not sure if this will happen with the 2026.2.3 version and the "Hidden" field or not?
But be careful when doing an update, and when running the config wizard, to make sure that all your alerts are still there!!
And Solarwinds folks, why does this stuff keep recurring?
