Duration of down time

[BeatMaster]

Hello!

I have made the trigger in Zabbix 1.0 which notifies me when icmp ping is 0 - router is down for 10minutes [trigger is ON] and send me the same message of ping status when triger goes OFF [ping is successful]. So i looked throught the time functions but can' t find answer: i want to get the action message which have the duration of time when the router was down, not the time when it get down. [The time between trigger status changes]

Thanks for any help

[BeatMaster]

looks like it is too complex

[Alexei]

No, it's not. It will require new macro, say {TRIGGER_IN_PREV_STATE} or similar, which would return time spent in previous trigger state.

It is not implemented yet.

[BeatMaster]

Yeah, it's what I wanted. So maybe it could be implemented in version 1.1? - it could be useful.

Alexei - thanks for the great stuff!Keep developing it and zabbix will be the best!

[bee]

{EVENT.AGE} = Duration of Problem/Downtime?

No, it's not. It will require new macro, say {TRIGGER_IN_PREV_STATE} or similar, which would return time spent in previous trigger state.

It is not implemented yet.

Hi ALexei,
Need to confirm with you, is macro {EVENT.AGE} can be use to represent duration of problem (Downtime)?
I've tried using macro {EVENT.AGE} and always return 0. Any suggestion? or i did missing something here?

Thanks,
BEE

[data7]

Event Age always returning "0"...

Hi ALexei,
Need to confirm with you, is macro {EVENT.AGE} can be use to represent duration of problem (Downtime)?
I've tried using macro {EVENT.AGE} and always return 0. Any suggestion? or i did missing something here?

Thanks,
BEE

Hello, this is happening to me too only on 1.6.2, bug confirmed?

I use these messages for notifications and both worked as expected until 1.6.1, on 1.6.2 it doesn't seem to exist any difference between {EVENT.DATE} and {DATE} and the same for {EVENT.TIME}. And as bee said above, the {EVENT.AGE} macro always returns "0"...

Here's what I use (with some mods, because of the language):

For Alerts:

Subject: Alert - {TRIGGER.NAME}

Text:
Problem: {TRIGGER.NAME}

Service: {ITEM.NAME}
Last received value: {{HOSTNAME}:{TRIGGER.KEY}.last(0)}

Host: {HOSTNAME}
IP: {IPADDRESS}

Date/Time of event: {EVENT.DATE} at {EVENT.TIME}

################################################## ############################

Subject: Recovery - {TRIGGER.NAME}

Recovered alert: {TRIGGER.NAME}

Date/time of problem start: {EVENT.DATE} at {EVENT.TIME}
Date/time of problem recovery: {DATE} at {TIME}
Problem length: {EVENT.AGE}

Service: {ITEM.NAME}
Last received value: {{HOSTNAME}:{TRIGGER.KEY}.last(0)}

Host: {HOSTNAME}
IP: {IPADDRESS}

#################################################

The output of the recovery (on 1.6 or 1.6.1) should be as the following:

Date/time of problem start: 2009.02.17 at 12:08:19
Data/time of problem recovery: 2009.02.17 at 12:16:16
Problem length: 7m

But on 1.6.2 the output of the first two lines simply repeat and the length of the event is always "0".

Guess I'll be downgrading to 1.6.1...

Regards,

Gabriel

[Alexei]

{EVENT.AGE} displays age of the last event. For recovery messages {EVENT.AGE} will always show '0'.

In pre-1.6.3 we extended macro {HISTORY.LOG} so that it will display also age of the problem along with escalation details.

[Icenode]

Has there been a fix/workaround/new command for this yet so recovery messages can include event duration?

[orionweb]

Request opened @ https://support.zabbix.com/browse/ZBXNEXT-252 Vote for it to be fixed / implemented.

[bashman]

I would like to query all the trigger's down time within a week.