Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix inventory threshold rule preview description #3941

Merged
merged 2 commits into from
May 30, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified docs/en/observability/images/inventory-alert.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 2 additions & 6 deletions docs/en/observability/inventory-threshold-alert.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -35,16 +35,12 @@ You can also set advanced options such as the number of consecutive runs that mu
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
and a warning alert if memory usage is 90% or above.
The chart shows the results of applying the rule to the last 20 minutes of data.
Note that the chart time range is 20 times the value of the look-back window specified in the `FOR THE LAST` field.

[role="screenshot"]
image::images/inventory-alert.png[Inventory rule]

Before creating a rule, you can preview whether the conditions would have triggered the alert in the last
hour, day, week, or month.

[role="screenshot"]
image::images/alert-preview.png[Preview rules]

[discrete]
[[action-types-infrastructure]]
== Action types
Expand Down