mO SharemO Share

check_performance_trend

Extension Version:1.0.0
Supported SONARPLEX Version(s):5.1.1a or higher
Requires:---

Checks the latest value of an already monitored service against a historic value and compares the resulting difference against thresholds. This is especially useful to check for the growth or loss over a certain amount of time, e.g. for detecting abnormal fuel level drops.

Installation

See the Managing Extensions with the Administration Web Interface article for further information.

Configuration

The Plug-In checks already collected data from an existing service check, therefore the service check, e.g. "FUEL-LEVEL" must be configured before and it must have "Performance Data" enabled. The check_performance_trend uses the historical performance data of "FUEL-LEVEL".

On this page:

 

Use Case

You are currently monitoring your fuel tanks with a fuel sensor (e.g. ModBus based Sensor with azeti SONARPLEX 600/4300/7000 M) and you are aware of fuel theft. The Plug-In allows you to monitor the trend of the fuel level and to alarm you if the fuel level drop is unnormally high. You can define the thresholds by yourself and decide if you want to check the absolute numeric change or the percental change. It could also be used to alarm you if your power consumption raises to fast.

Settings

SettingDescription
Name of the serviceThe service name as you configured it before . Must be identically written and is case sensitive.
Normal check intervalThe check interval that was configured for that service. Please choose the same or a multiple of the original service check interval . If the interval is "1" it will be automatically doubled internally to avoid measurement errors.
Look backHow many minutes to look back into the historical data.
Check typeWhat type of difference should be checked. This can be either the actual numeric or the percental change between the latest and the historic value.
Warning thresholdThis is the warning threshold. Must be positive if you want to check for a growth in value and must be negative to check for a loss. For example a warning threshold of "-10" would mean a drop by "10".
Critical thresholdThe critical threshold. Must be positive if you want to check for a growth in value and must be negative to check for a loss.
UnitThe unit of measurement, e.g. "gallons" or "cubics". Enter "debug" to enable debugging information. You can view the log file in the administrative web GUI under Status :: Logs :: azeti_addons.log.



The following macros are not currently supported in the footer:
  • style