There are a lot of changes here:
-Fixed a lot of issues encountered during my testing
-JSON path is evaluated BEFORE making comparisons (this was the true intended behavior by @chakflying)
-Variable name changes (cosmetic)
-Added != operator
-Changed jsonQueryDescription (again)
"Hostname or IP Address":"Hostname or IP Address",
@ -577,7 +577,7 @@
"notificationDescription":"Notifications must be assigned to a monitor to function.",
"keywordDescription":"Search keyword in plain HTML or JSON response. The search is case-sensitive.",
"invertKeywordDescription":"Look for the keyword to be absent rather than present.",
"jsonQueryDescription":"Use JSON query to parse and extract specific data from the server's JSON response. Compare the evaluated query against the expected value after converting it into a string. Refer to {0} for detailed documentation on the query language or experiment with queries using the {1}.",
"jsonQueryDescription":"Parse and extract specific data from the server's JSON response using JSON query or use \"$\" for the raw response, if not expecting JSON. The result is then compared to the expected value, as strings. See {0} for documentation and use {1} to experiment with queries.",
"backupDescription":"You can backup all monitors and notifications into a JSON file.",
"backupDescription2":"Note: history and event data is not included.",
"backupDescription3":"Sensitive data such as notification tokens are included in the export file; please store export securely.",