The most recent content from our members.
If you already have anomaly-based alert definitions created, it is difficult to see which nodes are selected as a part of the condition. This is especially so if you have thousands of nodes in your environment. When you create an anomaly-based alert, you have to select which nodes are a part of each alert definition one by…
I was thinking about potential use cases where I would trust a Generative AI to do something useful. I don't really expect a whole lot from them except for them to be able to create reasonably believable lines of text so i was thinking of where I spend the most time trying to write sentences in Orion. The OOTB alert…
Currently, to create an anomaly-based alert, you need to select the individual nodes that you want to include in the alert one at a time. The ability to create dynamic selection rules or even a select all option from the node picker would make life a lot easier.
For CPU/Memory anomaly based alerts, the conditions only allows for "is anomalous" and a percentage-based condition. A node-based CPU/Memory threshold would be a lot more useful than a static percentage. Even the option of less than xxx bytes free memory would be better than a percentage, being capacity on a node can range…
It looks like you're new here. Sign in or register to get started.