Skip to content

Commit

Permalink
[DOCS] Add advanced options in inventory rule
Browse files Browse the repository at this point in the history
  • Loading branch information
lcawl committed Mar 12, 2024
1 parent 033a884 commit 5622afd
Showing 1 changed file with 1 addition and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@ Conditions for each rule can be applied to specific metrics relating to the inve
You can choose the aggregation type, the metric, and by including a warning threshold value, you can be
alerted on multiple threshold values based on severity scores. When creating the rule, you can still get
notified if no data is returned for the specific metric or if the rule fails to query {es}.
You can also set advanced options such as the number of consecutive runs that must meet the rule conditions before an alert occurs.

In this example, Kubernetes Pods is the selected inventory type. The conditions state that you will receive
a critical alert for any pods within the `ingress-nginx` namespace with a memory usage of 95% or above
Expand Down

0 comments on commit 5622afd

Please sign in to comment.