Zabbix 4.0 中动作条件类型的等价物
Equivalents for the action conditions types in Zabbix 4.0
我需要过滤一些操作条件。在 3.0 版中,我使用条件类型的过滤对其进行了调整:
"filter": {
"evaltype": "0",
"conditions": [
{ "conditiontype": "16", "operator": "7", "value": "", "formulaid": "A" }, { "conditiontype": "5", "operator": "0", "value": "1", "formulaid": "B" }
]
}
但是在Zabbix 4.0中没有触发值(16)和维护(5)这样的类型,所以我怎么能替换它们?
条件类型 5
是 trigger value
,16
是 maintenance
- 看起来你在描述中交换了它们。
条件类型 5
已删除 in Zabbix 3.2, along with support for trigger value filtering on "OK" values in the frontend - all actions now kick off on PROBLEM events only (although there are recovery operations now). As you were filtering for trigger value of 1 which is PROBLEM,这意味着您可以简单地使用 Zabbix 4.0 删除该条件。
条件类型 16
已重命名为 problem is suppressed
in Zabbix 4.0,但它的工作方式应该与以前类似。
我需要过滤一些操作条件。在 3.0 版中,我使用条件类型的过滤对其进行了调整:
"filter": {
"evaltype": "0",
"conditions": [
{ "conditiontype": "16", "operator": "7", "value": "", "formulaid": "A" }, { "conditiontype": "5", "operator": "0", "value": "1", "formulaid": "B" }
]
}
但是在Zabbix 4.0中没有触发值(16)和维护(5)这样的类型,所以我怎么能替换它们?
条件类型 5
是 trigger value
,16
是 maintenance
- 看起来你在描述中交换了它们。
条件类型 5
已删除 in Zabbix 3.2, along with support for trigger value filtering on "OK" values in the frontend - all actions now kick off on PROBLEM events only (although there are recovery operations now). As you were filtering for trigger value of 1 which is PROBLEM,这意味着您可以简单地使用 Zabbix 4.0 删除该条件。
条件类型 16
已重命名为 problem is suppressed
in Zabbix 4.0,但它的工作方式应该与以前类似。