Problem Interval

[tomdom]

Hi,

I want my item checked every day from 7:00 am to 8:00 am.
my config:


I don't understand why zabbix checks it additionally at 00:00:29. It cannot do this because the device does not change state until 7:00 am

[cyber]

Is your regular interval set to 0?

[Hamardaban]

Look at the latest data, not the problem notifications. Is there any data received outside the schedule period?

[tomdom]

My interval set "60m", I will change to 0

[cyber]

One more thing... your item is checked only twice with this schedule. at 7 and at 8. If you want more checks there, you should add m/XXXX also.

[tomdom]

I understand, thank you again for your help.

[tomdom]

Hey Cyber, unfortunately zabbix checked the item again at 00:00:29. I do not know why.


My configuration:

[cyber]

You are showing item config, but you have a trigger popping up.. Maybe you should show us the trigger config instead?

[tomdom]

Ok, trigger configuration

[Hamardaban]

As I have already written to you - it's not about incoming (no incoming) data, but something else. You ignored it.
RTFM!
https://www.zabbix.com/documentation...onfig/triggers

Time-based functions are nodata(), date(), dayofmonth(), dayofweek(), time(), now()); they are recalculated every 30 seconds by the Zabbix history syncer process.

[tomdom]

I've seen the manual, but still don't understand. The item is checked at 00:00:20 - 00:00:30 then and 7:00 by the set value and that's OK, I changed the value of the checked file manually after 8 o'clock the value is not checked anymore. What should I do? How to set it up?

[Hamardaban]

The expression of the schedule for checking (receiving) data by the item you have written correctly.
The data will be requested from the agent every day at 7:00 and 8:00.
The next step is to check in the "latest data" (https://www.zabbix.com/documentation...ng/latest_data) that the data is received and they are correct.
Then proceed to setting up the trigger - what exactly are you trying to control? So far, your trigger expression looks abnormal.
Without having the data that receives these and without knowing your idea - it is impossible to assess the correctness of the trigger.
Now you look at the events generated by the trigger and wonder at the nonsense....

[cyber]

I guess that check returns date... in similar format as date() (YYYYMMDD). and of course half an minute (as Hamardaban pointed out time based function recalculation) after midnight it will not match..:P as last data is from previous day... As we see from first post, problem resolved some time in the morning, when new timestamp arrived and that expression turned false again..

Problem is not your item, but your trigger expression.

[tomdom]

Item checks the date and compares it to see if rsync was backed up today. Thank you already understand.