Hi Dojo,
I’ve noticed that in some cases, “Name changed” alarm type is detected by DM. I would like to understand when this type arise, because in case shared below, there’s no changes on the name:
Thanks!
Hi Daniel,
You get a “name changed” alarm when the name of the element changes or when the name of the parameter changes. Could you check if there is a name change of the element or parameter between this alarm and the previous one.
If there is no change between the alarms, best way is to load the information events from that timespan and see what happens around that time.
Hi Daniel,
In that case I suggest to create a ticket so we can investigate why the correlation alarm has a name changed alarm in its tree as it looks like a bug .
Understood, thanks for your help.
Given that this is a correlated alarm, probably one of the alarms that contributed to the correlation alarm is linked to a parameter of which the name was changed. You should be able to see the difference if you check the children of the correlation alarms on the parameter name column.
Hi Toon,
I haven’t found changes on children alarms. It seems that after DM restart, the correlation engine recalculate the present correlated alarms on the system but with this alarm type. Is it a possibility?
Hi Michaël,
I’ve checked that a manual DataMiner restart was launched. It seems that when DM start and correlated alarms was calculated, “name changed” alarms appeared, but there wasn’t any changes on the name.
I also checked the information events on that timespan and there isn’t something strange.