Sema 3.2 Suppression Rule Ordering and Hierarchy Gap

Sema 3.2 Suppression Rule Ordering and Hierarchy Gap

In Sema 3.2 the alerting module introduces a suppression rule engine that silences repeated alerts from the same source within a configurable window. The rules are evaluated before the notification engine, which should reduce noise but also requires a clear ordering when multiple rules apply.

Current UI constraints allow only one suppression rule per alert type, and there is no documented inheritance to child alert types. This limitation creates ambiguity when an alert hierarchy exists: a parent rule does not automatically propagate, and adding a new child type requires manual rule duplication.

Because the rule engine processes rules sequentially, the lack of a defined precedence between multiple rules on the same alert type is a potential source of inconsistent suppression. The documentation does not specify how to override or prioritize rules when both exist.

What is the internal precedence algorithm for multiple suppression rules on the same alert type in Sema 3.2?

Does the suppression rule engine support rule inheritance to child alert types, and if not, what is the recommended approach?

How can the UI be extended to expose rule hierarchy without breaking existing configurations?