78
If you run many probes concurrently you may want to
79
prevent them from hitting your network all at the same
80
time. Using the probe-specific offset parameter you
81
can change the point in time when each probe will be
82
run. Offset is specified in % of total interval, or
83
alternatively as 'random', and the offset from the
84
'General' section is used if nothing is specified
85
here. Note that this does NOT influence the rrds
86
itself, it is just a matter of when data acqusition is
87
initiated. (This variable is only applicable if the
88
variable 'concurrentprobes' is set in the 'General'
79
If you run many probes concurrently you may want to prevent them
80
from hitting your network all at the same time. Using the probe-
81
specific offset parameter you can change the point in time when
82
each probe will be run. Offset is specified in % of total interval,
83
or alternatively as 'random', and the offset from the 'General'
84
section is used if nothing is specified here. Note that this does
85
NOT influence the rrds itself, it is just a matter of when data
86
acqusition is initiated. (This variable is only applicable if the
87
variable 'concurrentprobes' is set in the 'General' section.)
94
Duration of the base interval that this probe should
95
use, if different from the one specified in the
96
'Database' section. Note that the step in the RRD
97
files is fixed when they are originally generated, and
98
if you change the step parameter afterwards, you'll
99
have to delete the old RRD files or somehow convert
100
them. (This variable is only applicable if the vari-
101
able 'concurrentprobes' is set in the 'General' sec-
92
Duration of the base interval that this probe should use, if dif-
93
ferent from the one specified in the 'Database' section. Note that
94
the step in the RRD files is fixed when they are originally gener-
95
ated, and if you change the step parameter afterwards, you'll have
96
to delete the old RRD files or somehow convert them. (This variable
97
is only applicable if the variable 'concurrentprobes' is set in the
104
100
Example value: 300
106
102
Supported target-specific variables:
105
The _e_c_h_o_p_i_n_g(1) "-R" option: Accept HTTP status codes 3xx
106
(redirections) as normal responses instead of treating them as
107
errors. Note that this option is only available starting with
110
Enabled if the value is anything other than 'no' or '0'.
109
Any extra options specified here will be passed unmod-
110
ified to _e_c_h_o_p_i_n_g(1).
115
Any extra options specified here will be passed unmodified to
112
Example value: -some-let-
113
ter-the-author-did-not-think-of
118
Example value: -some-letter-the-author-did-not-think-of
116
The _e_c_h_o_p_i_n_g(1) "-A" option: force the proxy to ignore
117
the cache. Enabled if the value is anything other
121
The _e_c_h_o_p_i_n_g(1) "-A" option: force the proxy to ignore the cache.
122
Enabled if the value is anything other than 'no' or '0'.
120
124
Example value: yes
123
The IP protocol used. Possible values are "4" and "6".
124
Passed to _e_c_h_o_p_i_n_g(1) as the "-4" or "-6" options.
127
The IP protocol used. Possible values are "4" and "6". Passed to
128
_e_c_h_o_p_i_n_g(1) as the "-4" or "-6" options.
129
How many pings should be sent to each target, if dif-
130
ferent from the global value specified in the Database
131
section. Note that the number of pings in the RRD
132
files is fixed when they are originally generated, and
133
if you change this parameter afterwards, you'll have
133
How many pings should be sent to each target, if different from the
134
global value specified in the Database section. Note that the num-
135
ber of pings in the RRD files is fixed when they are originally
136
generated, and if you change this parameter afterwards, you'll have
134
137
to delete the old RRD files or somehow convert them.
added
removed
doc/Smokeping/probes/EchoPingHttps.txt
