✨ feat: json-query monitor added

[mhkarimi1383]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

Resolves #2431
Resolves #3163
Resolves #3299

Adding json query monitor to add json query monitor and comparing json path value with expected value

Query should be according to json-query from jsonata docs see: http://docs.jsonata.org/simple

Type of change

Please delete any options that are not relevant.

• User interface (UI)
• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas
  (including JSDoc for methods)
• My changes generate no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

[CommanderStorm]

Could you go into if this resolves #2431 ?
(if yes: add Resolves #2431 to the description)

[CommanderStorm]

Another issue: json-query had its last commit in 2017 and seems abandoned.

Please go into

• why you chose this libary
• why you think this is still a viable option and
• none of the alternatives (at least those mentioned in https://github.com/auditassistant/json-query/issues/64) are viable

[mhkarimi1383]

Another issue: json-query had its last commit in 2017 and seems abandoned.

Please go into

* why you chose this libary

* why you think this is still a viable option and

* none of the alternatives (at least those mentioned in [library replacement auditassistant/json-query#64](https://github.com/auditassistant/json-query/issues/64)) are viable

I have just seen that this was the only option when searched for jq (json query) for JS

Now, I have switched to jsonata (Also: github and npm), I think this one is a great choice since it has more features, etc.

[CommanderStorm]

Two minor change-requests which came up in other issues:

• Could you also add Resolves #3299 to the description?
• Could you add this feature to the Readme (under Monitoring uptime for)? (https://github.com/louislam/uptime-kuma#-features) ^^

[mhkarimi1383]

My editor removed some white spaces at the end of lines ;)

Tests are getting 429 (rate limit) errors from GitHub and need retry

[mhkarimi1383]

Can you please confirm my last Merge from master?

I got some conflicts that I resolved

[louislam]

Can you please confirm my last Merge from master?

I got some conflicts that I resolved

Oh, I'm apologize, I forgot I shouldn't rebase the master branch. Let me fix it.

[CommanderStorm]

Again me:
Could you please add Resolves #3163 to the description?

[mhkarimi1383]

@louislam I think I have to rebuild the package lock in this branch since it got conflicts

[samumatic]

The Expected Value field is only accepting one value, but if i have multiple values, it fails and states:
[DOWN] 200 - OK, but value is not equal to expected value, value was: [1]

But i want it to be up, at the values 0&1, but down at the Value 2 or else.
I didn't found any option via syntax to bypass this problem.
Help would be appreciated.

[chakflying]

Have you tried using expressions in jsonata?

https://docs.jsonata.org/expressions

[mhkarimi1383]

The Expected Value field is only accepting one value, but if i have multiple values, it fails and states:
[DOWN] 200 - OK, but value is not equal to expected value, value was: [1]

But i want it to be up, at the values 0&1, but down at the Value 2 or else.
I didn't found any option via syntax to bypass this problem.
Help would be appreciated.

It would be great if you can change value

For example up and ok will be converted to ok

[samumatic]

Have you tried using expressions in jsonata?

https://docs.jsonata.org/expressions

Thank you for the hint, after a bit try and error i found the solution to my problem:

Json Query: ($.extensions.state = 0) or ($.extensions.state = 1)
Expected Value: true

Thank you for your fast response!

[jbates58]

Hi all, i would like to propose a feature for this, where if you get an unexpected response, and it marks the item as down, that it stores the entire JSON object so you can retrospectively look at what the error was.

I can see that it tells me what the response it got was which is fine, but the error message itself is stored in another JSON key in alot of things.

the response typically looks like this
{ "state": "unhealthy", "messages": [ "error", "mesage", "list", "here" ] }

[CommanderStorm]

please dont necropost on merged issues and have instead search for the respective issue and subscribe there ^^