-
Problem report
-
Resolution: Fixed
-
Major
-
6.0.24, 6.4.9, 7.0.0alpha9
-
Sprint 107 (Dec 2023), Sprint candidates, S2401
-
0.1
Steps to reproduce:
- Use monitoring by Acronis Cyber Protect Cloud MSP by HTTP
- Wail for items in Acronis CPC: Get devices: Acronis CPC: Device discovery
- 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
- 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.
- 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.