[ZBXNEXT-5034] simulate a (complex) trigger on historical data to see the effect Created: 2019 Feb 13 Updated: 2019 Feb 13 |
|
| Status: | Open |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Christophe Vandeplas | Assignee: | Valdis Murzins |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When writing more complex trigger expression it is sometimes though to identify the subtlety needed in the expression. For example if you're monitoring for slower response times. It would be great if we could write our expression, and then ask Zabbix to "simulate" the newly written expression/trigger on the historical data that we have in the database. This way we could assess if that expression would correctly match what we want to match, and does not match what it should not match.
|
| Comments |
| Comment by richlv [ 2019 Feb 13 ] |
|
How would this differ from the trigger testing feature? |
| Comment by Christophe Vandeplas [ 2019 Feb 13 ] |
|
As far as I understand the trigger testing just verifies the result based on a manual simulation of a specific condition. However if you have a complex expression that combines a larger dataset (combination of min(#5), max(), avg and such), you need many simulations to see the impact of the full expression. And what better simulation than the real data you've already been collecting? So if you already have the items collecting data, you could use this data to verify against the expression/trigger. I hope this explanation clarifies the motivation a bit. |