[RELEASE] thold-0.4.4-43

[sodium]

do a thold database upgrade

Code: Select all

goto <cacti dir>/plugins/thold/extras

Code: Select all

 php5 upgrade.php 

(to force the updates to the database) -- run as CACTI user

[ocoralan]

Thank you for your quickly reply, sodium.

I newly installedon another machine (Windows XP, Cacti 0.8.7g, PA 2., the error occurs again.

Code: Select all

05/20/2011 01:33:42 PM - CMDPHP: Poller[0] ERROR: A DB Exec Failed!, Error:'1060', SQL:"ALTER TABLE thold_data ADD COLUMN bl_thold_valid INT UNSIGNED NOT NULL DEFAULT 0'

[sodium]

have you done the forced upgrade?

[Wizzer]

What is the proper way to upgrade the Threshold plugin from a previous version?

[sodium]

What is the proper way to upgrade the Threshold plugin from a previous version?

there is no good way but this works for me

rename the old <path to cacti>/plugins/thold to <path to cacti>/plugins/thold.old
unpack the new thold (thus recreating the <path to cacti>/plugins/thold dir)
cd <path to cacti>/plugins/thold/extras/
php upgrade.php

[cigamit]

I generally just override the files, and then from there it should auto-upgrade when ever you visit any thold page, as long as the upgrade process was written correctly.


BTW, thanks for all these fixes, I merged them into the stable branch last week or so. Just attempting to do a bit more testing before I spit out a new version. I also need to ensure that an upgrade process is in place for people converting old baselines to the changes.

[sodium]

BTW, thanks for all these fixes, I merged them into the stable branch last week or so. Just attempting to do a bit more testing before I spit out a new version. I also need to ensure that an upgrade process is in place for people converting old baselines to the changes.

Cool There is 1 small fix in our tree and i'll post it next week. Thanks for the merge in main

[sodium]

released thold-0.4.4-43

with only 1 fix: Fix undefined index messages when save Hi/Low or Timebased thresholds

have fun

[noname]

'friendly_name' is not identical between sources.

thold.php:

'bl_ref_time_range' => array(
'friendly_name' => 'Time range',
'method' => 'drop_array',
'array' => $reference_types,
'default' => read_config_option('alert_bl_timerange_def'),
'description' => 'Specifies the point in the past (based on rrd resolution) that will be used as a reference',
'value' => isset($thold_item_data['bl_ref_time_range']) ? $thold_item_data['bl_ref_time_range'] : ''
),

thold_templates.php:

'bl_ref_time_range' => array(
'friendly_name' => 'Time reference in the past',
'method' => 'drop_array',
'array' => $reference_types,
'default' => read_config_option('alert_bl_timerange_def'),
'description' => 'Specifies the point in the past (based on rrd resolution) that will be used as a reference',
'value' => isset($thold_item_data['bl_ref_time_range']) ? $thold_item_data['bl_ref_time_range'] : ''
),

I guess the former ('Time range') is correct.

[sodium]

'friendly_name' is not identical between sources.
[...]
I guess the former ('Time range') is correct.

Nope the whole code for thresholding (baseline) changed and now it is reference in the past...

[noname]

Nope the whole code for thresholding (baseline) changed and now it is reference in the past...

Really? Oh... I'll have to rewrite this figure again (;_;)

[sodium]

Nope the whole code for thresholding (baseline) changed and now it is reference in the past...

Really? Oh... I'll have to rewrite this figure again (;_;)

nope the last post describes the current behavior and the reason why we changed it is that we have to do some 50000+ thold checks at every poll
in the past the reference was calculated at every poll (reading 288 values, do a hi/lo) and compare.
IMHO this is no baseline so we changed the code to the new (current) code

[noname]

Nope the whole code for thresholding (baseline) changed and now it is reference in the past...

Really? Oh... I'll have to rewrite this figure again (;_;)

nope the last post describes the current behavior and the reason why we changed it is that we have to do some 50000+ thold checks at every poll
in the past the reference was calculated at every poll (reading 288 values, do a hi/lo) and compare.
IMHO this is no baseline so we changed the code to the new (current) code

Ah, I see. Thanks for describing.

Then, the figure which I posted is correct?
Sometimes I have misunderstanding due to my lacking of language skills...

[sodium]

what you describe is almost correct
we determine the rrd steps (normally 5min, 30min, 2hour, 1day) and offer this list of steps (without the current 5 min) as the reference in the past.
this determination is done by reading the (from the rrd file) average back and store it in the database for the validity of the measurement. (thus @ 00.00 hour the new value is placed in the database -- for 1 day average)
every 5 mins we compare the current value with the average stored and determine the % deviation
and this is done to minimize the cpu power needed to check the values

have fun

[noname]

Thanks sodium! ^^
I've replaced the screenshot and some descriptions.