https://mmonit.com/monit/documentation/#TIMESTAMP-TEST It may look to you totally clear, because, you already know correct meaning, but for a new person definition is ambiguous and unclear, even if new person thinks he got it clear he may be wrong.
Problem is you never explain explicitly what time stamp tested against which date in what way.
For example test
if timestamp < 1 day then alert could be interpreted as 'this file timestamp is older than one day in compare to now, because, it's smaller value', but from stated example:
For example testing directory for file addition or removal: check directory bar path /foo/bar if timestamp < 1 hour then alert
it could be understood that
< 1 meant fresher, so it could be inferred as 'time difference is smaller than 1 hour'. See, these are completely opposite meanings to compare operators.
It seems also naming
timestamp is confusing, because, it's not time stamp, but time delta.
It never stated which timestamp is checked, it's confusing, because, there is many timestamps in filesystem. Person could download file from other server, updating
ctime on each download, but
mtime is not changed. But person may be interested in checking exactly
mtime to see if file is stale, old, obsoleted, not updated. It is not possible with monit to select which timestamp to check.
I feature request possibility to select which timestamp (mtime, ctime, or atime) to test. And if not specified it could fall back to default behavior (whatever it is, I didn't understand from the docs too).