hi there,
Hi there,
Can someone explain on how to configure Baseline monitoring using THOLD?
And also the fields of the baseline settings
Threshold Type
The type of Threshold that will be monitored.High / Low Values Baseline Time Based --this is Baseline
Baseline Settings
Baseline monitoring
When enabled, baseline monitoring checks the current data source value against a value in the past. The available range of values is retrieved and a minimum and maximum values are taken as a respective baseline reference. The precedence however is on the "hard" thresholds above. Baseline monitoring
Reference in the past
Specifies the relative point in the past that will be used as a reference. The value represents seconds, so for a day you would specify 86400, for a week 604800, etc. - does it mean that it only look for the specific day that was specified?
Say specified 1 week- is it looking for the data from this time a week ago?
Time range
Specifies the time range of values in seconds to be taken from the reference in the past— isnt this the same as the above?
Baseline deviation UP
Specifies allowed deviation in percentage for the upper bound threshold. If not set, upper bound threshold will not be checked at all.- if I only want to be alerted if the load reached100% will I put100 here?
Baseline deviation DOWN
Specifies allowed deviation in percentage for the lower bound threshold. If not set, lower bound threshold will not be checked at all.-- im leaving this blank but when you hit save, its defaulting to 0- and its giving me alerts when the percentage goes down a little over 1%
Baseline Trigger Count
Number of consecutive times the data source must be in breach of the baseline threshold for an alert to be raised.
is there a good thold documentation? I cant seem to find anything substantial.
THOLD Baseline config
Moderators: Developers, Moderators
THOLD Baseline config
- Attachments
-
- Screen shot 2011-01-11 at 5.34.27 PM.png (109.61 KiB) Viewed 11118 times
Re: THOLD Baseline config
I understand baseline monitoring like this(*).
Is it correct?
(*) Sorry, the figure first I posted was definitely wrong.
Is it correct?
(*) Sorry, the figure first I posted was definitely wrong.
Re: THOLD Baseline config
Cool Picture!!
For example:
Now is 4/27 6:00, you set "Reference in the past" is 86400(24H) and "Time range" is 10800(3H)
so "Reference in the past" is 4/26 6:00
"Time range" is 4/26 3:00~6:00
The maximum and minimum value are in the "Time range"
If max value is 50 ,min value is 10 and set "Baseline deviation UP" = 100, "Baseline deviation DOWN" = 50
The trigger UP value is 50 + (50*(100/100)) = 100
The trigger DOWN value is 10 - (10*(50*/100) )= 5
If current value is greater than trigger UP value and exceed trigger count, then thold will send alert, and vice versa.
For example:
Now is 4/27 6:00, you set "Reference in the past" is 86400(24H) and "Time range" is 10800(3H)
so "Reference in the past" is 4/26 6:00
"Time range" is 4/26 3:00~6:00
The maximum and minimum value are in the "Time range"
If max value is 50 ,min value is 10 and set "Baseline deviation UP" = 100, "Baseline deviation DOWN" = 50
The trigger UP value is 50 + (50*(100/100)) = 100
The trigger DOWN value is 10 - (10*(50*/100) )= 5
If current value is greater than trigger UP value and exceed trigger count, then thold will send alert, and vice versa.
Re: THOLD Baseline config
Since thold-0.4.4-??? (not sure), it seems baseline monitoring was changed its behavior.
As far as I read source, like this: (If I have misunderstanding, please point out..)
Baseline settings: (e.g. thold-0.4.4-41)
New baseline threshold works based on RRA resolution "in the past" which is associated in the given datasource.
("30 Minutes", "2 Hours" and "1 Day" is corresponded to each RRA -- "Weekly", "Monthly" and "Yearly")
If you modified RRA settings, probably the above choices are also changed.
"Time range" won't be used.
"Time reference in the past" is not referenced the exact times (e.g. 30 minutes) before. It is adjusted to fits the boundaries of given time from midnight (0:00).
With this change, number of step for calculating values to compare are reduced drastically. (Thanks sodium for detailed explanation)
(But personally, I like the former(0.4.3) style..)
// Sorry my English
EDIT: replaced screenshot & some descriptions
As far as I read source, like this: (If I have misunderstanding, please point out..)
Baseline settings: (e.g. thold-0.4.4-41)
New baseline threshold works based on RRA resolution "in the past" which is associated in the given datasource.
("30 Minutes", "2 Hours" and "1 Day" is corresponded to each RRA -- "Weekly", "Monthly" and "Yearly")
If you modified RRA settings, probably the above choices are also changed.
"Time range" won't be used.
"Time reference in the past" is not referenced the exact times (e.g. 30 minutes) before. It is adjusted to fits the boundaries of given time from midnight (0:00).
With this change, number of step for calculating values to compare are reduced drastically. (Thanks sodium for detailed explanation)
(But personally, I like the former(0.4.3) style..)
// Sorry my English
EDIT: replaced screenshot & some descriptions
- TheWitness
- Developer
- Posts: 17047
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: THOLD Baseline config
In 0.4.6 the GUI will change just a little bit to articulate how this works. Plus it will actually report the deviation values in the GUI.
TheWitness
TheWitness
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Re: THOLD Baseline config
So is the deviation % now determined from the AVG value, and not MIN or MAX in a given time period?
Who is online
Users browsing this forum: No registered users and 0 guests