pflogsumm.pl: "no_bounce_detail" is depreciated, use "bounce_detail=0" instead
pflogsumm.pl: "no_deferral_detail" is depreciated, use "deferral_detail=0" instead
pflogsumm.pl: "no_reject_detail" is depreciated, use "reject_detail=0" instead
pflogsumm.pl: "no_smtpd_warnings" is depreciated, use "smtpd_warning_detail=0" instead
With the new option 'graph_mode' the values are, by default, shown with
absolute values. This new option permits switching between 'absolute' and
'rate'. #241
There was a stupid bug that prevented to include the SReclaimable value in the
formula to calculate the 'Used' value.
Morever, I've seen that newer versions of 'free' command also include the value
SUnreclaim in that formula. So, the final calculation of 'Used' is like this:
Used = MemTotal - MemFree - Buffers - Cached - SReclaimable - SUnreclaim
This ensures that Monitorix is in sync with the results of 'free' command. #204
From now on the user will have the opportunity to select which
command will use to gather the network status statistics. The
new option 'cmd' supports two values 'netstat' or 'ss', being
the later the value by default.
If the 'cmd' option is not defined, then the command line used
will be 'ss', that's because in newer Linux systems it looks like
the command 'netstat' is being deprecated.
In older Linux systems people will be forced to use the 'netstat'
command because, early 'ss' versions doesn't contain the protocol
column in its output, which breaks the regexp used to extract the
the values. #196
From now on, the alerts accepts a forth parameter that specifies
when the alert will be triggered. This parameter accepts two values:
'above' or 'below', being the 'above' the default value if it's not
specified, in order to keep backwards compatibility.
This way, if some value in the graph is 'above' or 'below' from the
threshold during more time than specified in the timeout value, the
alert will be triggered.
The manpage has also been updated to reflect this new feature. #221
From now on, the alerts accepts a forth parameter that specifies
when the alert will be triggered. This parameter accepts two values:
'above' or 'below', being the 'above' the default value if it's not
specified, in order to keep backwards compatibility.
This way, if some value in the graph is 'above' or 'below' from the
threshold during more time than specified in the timeout value, the
alert will be triggered.
#221