[ZBX-21943] Fix loss and latency checks in Cisco Meraki template Created: 2022 Nov 17  Updated: 2024 Apr 10  Resolved: 2022 Dec 02

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.2.4, 6.4.0beta3
Fix Version/s: 6.0.12rc1, 6.2.6rc1, 6.4.0beta5, 6.4 (plan)

Type: Problem report Priority: Trivial
Reporter: Vyacheslav Khaliev Assignee: Andrew Biba
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team INT
Story Points: 0.125

 Description   

Please add filters for loss and latency discovery in Cisco Meraki device by HTTP template. There is no data from API about loss and latency checks when the device is down.
Here is the example of API response when the device is down:
{
   "networkId":"L_620933798623721683",
   "serial":"Q2LY-3H9V-J2AG",
   "uplink":null,
   "ip":null,
   "timeSeries":[
     

{          "ts":"2022-11-17T07:00:52Z",          "lossPercent":null,          "latencyMs":null       }

   ]
}

This filters needed:

  • IP-address matches "((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)\.?\b){4}$" and not matches "^$";
  • uplink matches ".+" and not matches "^$".

Also please change preprocessing for loss and latency items. "Custom on fail" and set value to "-1" is needed in first step (jsonpath) to avoid unsupported items when the device is down. Javascript step is not needed in this case.



 Comments   
Comment by Andrew Biba [ 2022 Nov 30 ]

Resolved in:

Generated at Fri May 02 07:24:32 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.