[ZBX-23773] Template for "Acronis Cyber Protect Cloud MSP by HTTP" containing false positive triggers Created: 2023 Dec 01  Updated: 2024 Apr 10  Resolved: 2024 Feb 12

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.0.24, 6.4.9, 7.0.0alpha9
Fix Version/s: 6.0.27rc1, 6.4.12rc1, 7.0.0beta2, 7.0 (plan)

Type: Problem report Priority: Major
Reporter: Tomáš Heřmánek Assignee: Kristaps Naglis
Resolution: Fixed Votes: 0
Labels: acronis, http, template
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team INT
Sprint: Sprint 107 (Dec 2023), Sprint candidates, S2401
Story Points: 0.1

 Description   

Steps to reproduce:

  1. Use monitoring by Acronis Cyber Protect Cloud MSP by HTTP
  2. Wail for items in Acronis CPC: Get devices: Acronis CPC: Device discovery
  3. When your items starting to collecting data check data for acronis.cpc.device.backup.next[{*} {#NAME}

    {*}] this itmes gives you timestamp for next run of backup job

  4. Trigger last(/Acronis Cyber Protect Cloud MSP by HTTP/acronis.cpc.device.backup.next{#NAME}) < now() containing small error. Default item interval is 1min but function now() is time function which is calculated every time when zabbix received data + additionally another 30s. Every time we have for 30-40s fault positive, before we have new updated data with timestamp for next run.
  5. Trigger can be adjusted like this: last(/Acronis Cyber Protect Cloud MSP by HTTP/acronis.cpc.device.backup.next{#NAME}) < (now()+120)

Result:
Fail positive events in nights. Event is automatically closed after 30-40s.
Expected:
New event only when is backup not done for bigger period of time.



 Comments   
Comment by Kristaps Naglis [ 2024 Feb 06 ]

Fixed in:

Generated at Tue Jun 03 18:07:59 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.