Why do alerts on routing protocol neighbor down have different AlertObjectId in the DB everytime?

mibsinstanity

As it says in the title, I noticed that when alerts get triggered on routing neighbors they have a different AlertObjectId in the DB everytime. I'm looking in the AlertHistory table and I see the same (routing neighnor) alert on the same node having a different AlertObjectId, but if I look at a different type of alert (for example node is down) it's the same AlertObjectId whenever it happens on the same node.

I am trying to use these routing alerts to create a report about how much time the links where down and the facts that this Id has a different value every time is quite problematic.

mibsinstanity

So this seems like a bug, I changed the AlertObjectID in the AlertHistory table from the database to match the latest ID associated with the respective neighbor on that node and now I can see all the instances of that alert triggered on the node.