Allow for More Than 2 Thresholds (and custom names, and colors) within Rules

[BenB196]

Describe the feature:

Currently, rules (i.e. Metric threshold) only have 2 "thresholds": Alert and Warning.

1. It would be nice to be able to have more than just 2 "thresholds"
2. It would be nice if you could set custom "threshold" values, as Warning and Alert aren't always the best descriptors.
3. It would be nice if you could set the color that the "threshold" value is, currently it's either yellow or red

Describe a specific use case for the feature:

Let's say I have a Metric threshold rule that monitors for the used disk space of systems. The rule checks the average of the value system.filesystem.used.pct.

I want to be able to do the following:

• At 90% used, I want an action to fire that creates a ticket within a ticketing system.
  • This can be called something like: Warning "threshold".
  • The color here could be yellow.
• At 95% used, I want an action to fire that sends an email to a team.
  • This can be called something like: High or (or ``) "threshold".
  • The color here could be orange.
• At 98% used, I want an action to fire that sends an SMS text message to an on-call person.
  • This can be called something like: Critical (or Hey, look at this ASAP) "threshold".
  • The color here could be red.
• At 99% used, I want an action to fire that send an SMS text message to an entire team.
  • This can be called something like: Dangerously Critical (or Things are going to break soon, look at this immediately) "threshold"
  • The color here could be neon pink

[BenB196]

This feature might now be covered under conditional actions:

Though if Elastic does want to consider this covered, it could probably use more official documentation.