In Cisco Meraki (https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/net/meraki_http) template there is an item meraki.device.status, and trigger “Meraki: Status is not online” has the following condition:

Alert is somehow misleading. Per Meraki API documentation, the possible values are:

"alerting", "dormant", "offline", "online"

By definition a device has to be online for it to be alerting which makes “Status is not online” somewhat misleading (we can provide an example of this if needed) as an offline device would generally constitute a major issue but an alerting device would generally be less serious.

Suggested preprocessing (and it’s associated value mapping) to be adjusted to return 3 if status is ‘alerting’ and then this trigger should be split:

Trigger 1: Meraki: Status is offline with the condition of last(//meraki.device.status)=0
Trigger 2: Meraki: Status is alerting with the condition of last(//meraki.device.status)=3

Thanks to andrew.harris for reporting!