because this functions returns 0 for cases when it's usually considered to be a PROBLEM, while other functions (or even all) return 1 for usual PROBLEM case
Zalex, while 'usually' here helps, i just wanted to mention that reversing 0 and 1 is easy - for example, with the net.*.port items one might monitor a port that tends to be open, but should be closed.
even with fuzzytime(), one might get file modification time in an item, and check for that time not to be recent - if that's an error log file and we are not doing full log monitoring on it.
note that nothing to change here, just a minor clarification - and examples are always good
Oleksiy Zagorskyi Hmm, indeed we could also mention key vfs.file.time[/path/file,modify]
In Examples we mention only functions, without possible items context, so reflecting logic =1 could be hard there and doesn't make much sense. Although, silly, but possible use case is vfs.file.time[/etc/passwd,modify].fuzzytime(3600)=1 - detect passwd file modification during last hour.
Suggested additional sentence (after "Usually ...") is:
Can be used also with vfs.file.time[/path/file,modify] key to check that file didn't get updates for long time.
Oleksiy Zagorskyi added, RESOLVED
Gunars Pujats CLOSED