Problems with time Interval in Items and delayed triggers?

[Minky]

Hello, I am currently looking for a monitoring tool for our company.
The most important things we need to be able to do is monitor if VMs are on, reachable, virtual hdds dont fill up to 100% and if certain Windows Services are running.
Those are the most important things and as far as I know these things work perfectly fine in my testvm with zabbix installed.
I installed the zabbix agent on a windows server vm and it instantly picked up all the neccessary items including windows services. This is so fu..ing awesome and so much less of a hassle than the 2 other systems I tried before zabbix.
It does recognize all the items and changes in their values properly, displays the warnings if triggers are triggered and I managed to set up mail alerts.
So far I absolutely love this tool and so many things that barely worked in other systems are a 2 minute setup here.
But I found a few things about the triggers/alerts that I dont quite understand and thus hit my first roadblock and I hope someone here can clarify that for me, since the solution is probably pretty easy.

When I switch off a monitored service or fill up my hard drive on purpose I can even see in the graph under latest data that the value crosses the limit of alerting, but the alert appears about 3 minutes later, like it takes a average over multiple data points or it waits for it to cross the value over a certain amount of time or a number of checks. The other thing I saw is if I open an item, for example a certain service running on the windows vm, there is an interval listed for 1m, but I am not able to change it. And for other items like the c drive fill state there is no interval.

So if possible I´d like someone to explain to me the most easy way to adjust the time interval so I can have very critical services or services that we need to monitor more closely for whatever reaseons to eG 5 seconds, and others that dont need that ammount of checks to once every 3 minutes or so and why some of the alerts do what I described above and if possible how I can change that specific trigger to instantly report the hdd fill state instead of after multiple checks.
I can see so many options in triggers and items but I am not allowed to change any of them which doesnt make any sense to me.

[Minky]

Can anyone help?

[cyber]

A month has passed and you have not figured it out yet?

So you are using that OOB windows template? It creates service monitoring based on discovery, using prototypes. All of those items/triggers are with same severity/check time, because .. prototype!
Out of the box templates are good for quick startup, but when you need somthing else, you need to dive into modifications... Clone that template, configure it to pickup only required services, might need more than one discovery to be able to use different prototypes...Play around with overrides in disccovery...

filesystem fillup trigger is not just "last()>X" .. it is a bit more complex..

last(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},pused])>{$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} and
((last(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},total])-last(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},used]))<{$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"} or timeleft(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},pused],1h,100)<1d)

So it might not react right away, but also avoids some false positives...

[Minky]

A month has passed and you have not figured it out yet?

So you are using that OOB windows template? It creates service monitoring based on discovery, using prototypes. All of those items/triggers are with same severity/check time, because .. prototype!
Out of the box templates are good for quick startup, but when you need somthing else, you need to dive into modifications... Clone that template, configure it to pickup only required services, might need more than one discovery to be able to use different prototypes...Play around with overrides in disccovery...

filesystem fillup trigger is not just "last()>X" .. it is a bit more complex..

last(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},pused])>{$VFS.FS.PUSED.MAX.CRIT:"{#FSNAME}"} and
((last(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},total])-last(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},used]))<{$VFS.FS.FREE.MIN.CRIT:"{#FSNAME}"} or timeleft(/Windows by Zabbix agent active/vfs.fs.dependent.size[{#FSNAME},pused],1h,100)<1d)

So it might not react right away, but also avoids some false positives...

Thanks a lot for your answer.
No I didn´t figure it out.
I tried some stuff for a few hours and then didn´t feel like wasting more time. I already requested a standalone server for this project and an LTE Router, since Zabbix can apparently be configured to send AT commands to the router which then sends SMS instead of zabbix sending the sms directly, so we have some extra ways of sending alerts. Unfortunately the vendors take a long time and I´ve basically been waiting arround for 3 weeks now spending my time on other projects.

Thanks a lot again for your help. I hope I will be able to test it soon.
I´m really looking forward to deploying the server and setting everything up.
Unfortunately I dont know a lot about monitoring and many things zabbix does or rather the ways it does it seem a bit confusing to me, so you will certainly see some more stupid questions from me, but so far it seems like a really awesome tool if you manage to set it up correctly and understand how it works.

[cyber]

Questions ain't stupid as long as you have tried to look for answers before asking.. Noone likes to answer topics like "I need this and that... with exact order of buttons pressed .... and pictures" ...
"I did this and that, did not work out, can I get some pointers?" ... yea, you will get them...

Zabbix manual will be your friend, but you can not read it starting from middle... many people find the topic, they are intrested in, but as they have not read the "basics", many things come as a surprise. And then they are angry, "why this stupid tool works like it works...I want it to work much different ways.."