Extended testing is an advanced feature. If you are just starting out with argus it is recommended that you stick to the standard built-in service tests as described in services
Most services (those places where it makes sense) can do various comparisons on the service’s result:
There are also several pre-processing and calculations that can be performed before testing
for example
Service TCP { uname: disk-space messagedn: /home is nearly full port: 6543 send: /home pluck: \s(\d+)% maxvalue: 90 } Service UDP/NTP { uname: dispersion messagedn: clock has drifted too far unpack: x8 N scale: 65536 maxvalue: 2 } Service UDP/DNS/Serial/example.com { minvalue: 2002010100 maxvalue: 2004123100 } Service TCP/URL { url: http://api.example.com/inventory.json jpath: $.store.book[0].price expr: x * 100 minvalue: 100 maxvalue: 200 } Service TCP/URL { url: http://api.example.com/inventory.xml xpath: /store/book[1]/price expr: x * 100 minvalue: 100 maxvalue: 200 }
Services can be checked for values outside of the predicted range using Holt Winters
All services which can make use of the extended tests can have the resulting value graphed. See the documentation on graphing.