Hi Elvio,

You mean then that if one would mask a service, that automatically DataMiner masks all underlying elements?  So all those elements would be masked then as a result, and hence all their active alarms, and new alarms on those would also be masked?  Just to make sure we understand exactly what you would expect in terms of functionality and behavior.

There is no such standard functionality, but then again this could potentially be done through an automation script.  But note that it could also depend a bit on how the services are constructed of how easy or complex that would be.  In general, a service can be anything from a very static collection of elements to a very dynamic collection of parts of elements. If it's dynamic (i.e. based on logic and conditions elements join and leave services automatically) then the question is if the element is only masked while it is included in the service, and it automatically unmasks probably when it leaves the service. If it's part of an element that is included in the service, then probably not the entire element can be masked when the service is masked, i.e. then only the metrics that could affect the masked service should also be masked.

But if you can elaborate a bit on what you had in mind, maybe some sort of solution can be advised.