Hi Catarina,

There is no direct workaround for the limitation that prevents using hysteresis and conditions together on the same parameter in a DataMiner alarm template.

A possible workaround is to use a correlation rule. With this approach, you can design a correlation rule that mimics hysteresis-like logic by monitoring sequences of alarm events or parameter changes and only triggering a correlated alarm when certain patterns (such as a persistent event where the condition remains fulfilled for a set duration) are met, while also applying additional conditions. Note that this will result in two alarms: the original parameter alarm and the correlated alarm if the rule matches.

However, this method is not a direct replacement for native hysteresis functionality and requires careful configuration and testing. Additionally, best practices recommend keeping correlation rules as efficient as possible to avoid performance issues