AO: Omission of rule params on rule details page makes it hard to distinguish rules from each other

[sorenlouv]

Problem

The rule details page currently does not surface any rule params. This makes it very difficult to figure out at a glance, what the rule is doing. For instance, a user may have created 10 different latency rules. Each rule could be for a specific service, transactions group or something else. From the rule details page, all 10 rules will look identical.

Scenario
A user has created 5 latency rules for 5 different services. The latency rule of Service C is firing too often so they want to increase the threshold. Right now the user cannot tell the rules apart because the rule details page doesn’t display contextual information like service name, environment, transaction name etc.

Solution

Surface rule params on the rule details page. Not all rules may be relevant to display, so perhaps it should be part of the rule type definition whether a given rule param is displayed in the details page. A simple boolean flag will do.

[elasticmachine]

Pinging @elastic/actionable-observability (Team: Actionable Observability)

[maryam-saeidi]

@maciejforcone @mdefazio Do you have any suggestions about improving this scenario and adding rule params in the Definition section?

[mdefazio]

This block is certainly in need of an update. I will add this as a topic for our create rule flow updates since we want to move into address the rule detail page more anyway.