Help understanding timeleft

[HeadQuaker]

Hello,
I've read the documentation about timeleft but there should be something I don't understand.
The need :
We have a DB with counters that go down. I need to use timeleft to get the time they reach 0.

I'am using the item like that : timeleft(/HOSTNAME/countersremaining[DBINSTANCE],7d,30d)
If I'am understanding, the item will predict the timeleft based on 30 days datas in 7 days ?

For example : if the result is 10 month, it means there will be 10 months left in 7 days ?

Regards

Bonjour,

J'ai lu la documentation concernant timeleft mais il y a quelque chose que je ne dois pas comprendre car la documentation ne correspond pas à la syntaxe.
J'explique :
Nous avons une BDD qui contient des compteurs qui diminuent avec le temps. Je voudrais avec timeleft connaitre le moment où un compteur atteindra 0.

Du coup voici mon item : timeleft(/HOSTNAME/countersremaining[DBINSTANCE],7d,30d)

Si je comprends bien, mon item va estimer un timeleft sur 30jours de données pour la situation dans 7 jours ?
Donc si le résultat est 1an ça veut dire que dans 7 jours il restera environ un an avant d'atteindre 0 ?

Merci

[HeadQuaker]

Well, some advice please?

[Atsushi]

If you want to know the time until it reaches 0, why not specify 0 for threshold? Please refer to the example in the manual.

https://www.zabbix.com/documentation/current/en/manual/appendix/functions/prediction#prediction-functions-1

[HeadQuaker]

Hello,

Like this ? timeleft(XXXX,30d,0)

[cyber]

Hello,

Like this ? timeleft(XXXX,30d,0)

yes, this calculates time (in seconds) that it will take for this value to reach 0, based on last 30d of data. Trigger, for example "timeleft(/host/item,30d,0)<86400", will fire, if it predicts, that it will reach 0 before 1 day (86400 seconds)

[HeadQuaker]

Ok thank you