URL monitoring shortcomings

[Former User]

I'm running what appears to be an old version of monit, but I don't see in the release notes for the latest revs evidence that the areas below have been addressed.

For URL monitors:

1. The logs don't show response time, so you can't review them (with the -v enabled) and answer questions like "What response time has this monitor been receiving in the recent past?" Other services (such as system) display the value of the last sample.

2. When there is a pattern mismatch, monit doesn't log the response payload received. Can you add it, or some portion of it to the logs?

3. When there is a pattern mismatch, monit doesn't expose the response payload in such a way that it could be included in an email alert. Combined with 2, you're running blind when a failure occurs. Can you add the response payload (or some subset of it) to a variable that can be accessed by an alert template?

4. Doesn't appear that monit logs or provides a way to reference HTTP status codes in email alerts.

Ex. config

check host foo address blah.blah.blah
  if failed icmp type echo
    count 3
    timeout 2 seconds
    5 times 5 cycles
  then alert
  if failed url https://blah.blah.blah/health
    content = '^\{"status":"UP",'
    timeout 7 seconds
    retry 3 times
    3 times 3 cycles

Thanks