Can't get time constraints on triggers to work

[drecaise]

I'm monitoring the last data in some databases. It's important that this data is current so whenever the last data is older than 45 minutes a trigger fires. However each night old data is cleaned from the database and no new data is inserted during this time. As it is normal that the data is behind more than 45 minutes at night I don't want the trigger to become true at those moments.

I am using the following trigger expression:

{CORP DWH:custom.dwh.delay.last(0)}>2700 & {CORP DWH:custom.dwh.delay.time(0)}>06300 & {CORP DWH:custom.dwh.delay.time(0)}<233000

However I still receive emails flagging the trigger fired at 01:46hrs

I'm not sure if I made a mistake in the definition or if this is a bug

I am running zabbix server 1.6.2 on CentOS 5.2
Data custom.dwh.delay is zabbix trapper data

Any help is greatly appreciated

[Neurotox]

Hi,

I normally use the time constraints on "actions" not on "triggers", I don't think it's possible to do it on "triggers".

In "actions" you could set something like: "Time period not in "1-7,01:00-04:00""

For my setup, I deactivate almost all nocs between 01:00 and 04:00 for one of my Zabbix servers.

My actions look like:

(A) and (B)
(A) Trigger severity >= "Average"
(B) Time period not in "1-7,01:00-04:00"

You will probably have to do something more complex. Probably you will have to exclude the specific triggers from your general action and then create a second action just for this triggers and set a time constraint on it.

I hope that will help you,
François

[Calimero]

{CORP DWH:custom.dwh.delay.last(0)}>2700 & {CORP DWH:custom.dwh.delay.time(0)}>06300 & {CORP DWH:custom.dwh.delay.time(0)}<233000

This should read '>063000' if you mean 'after 06:30:00'.

[drecaise]

This should read '>063000' if you mean 'after 06:30:00'.

Thanks Calimero! I completely overlooked that typo :$ I've changed it and will test it tomorrow as I lack the time now.

And thanks for the suggestion Neurotox. It isn't a very good solution anymore if you are counting alarms for SLA's. That's why I don't want to use the method you proposed. Your suggestion is appreciated though!

[Neurotox]

Thanks for the feed back. I have not think about SLA, I think I will change my setup