Hi Juan,

You could create two elements that point to the same device, and if the device / its API allows it, it will be polled twice, and you will two times the same device in DataMiner (that you can assign different Alarm Templates and all that),

But more interesting is maybe to use the element replication capability (Replicating elements | DataMiner Docs).  In that case, you will have a second element, which is the exact same as the first element – but the replicated element receives its data from the original element (i.e. the replicated element will not poll the data from the device itself again).  But on the replicated element you can configure a different alarm template, you can create correlation rules on that element, etc. (i.e. the replicated element only takes the parameter values from the original element).

Hope this is what you were looking for.

Thanks @ben.vandenberghe

I will replicate and create alarm template to monitor different parameters along with different correlation rule to send alerts to Slack on different channels.

I had originally attempted to group two alarm templates but that did not work. One alarm template monitored video, Audio , CC and the other monitored SCTE PGM start end on a schedule. I could not get that to work.

Ultimately I create one alarm template and used the Automation Script and scheduler to get that to work but now im losing alerts for the video . I’ll try your recommendation on  replicating the element and each will have its own alarm template and correlation rule.

I’ll work on this and post any updates