Allow JSON key matching for MQTT monitors #1050

New issue

Closed

opened 2026-02-28 02:08:18 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:08:18 -05:00

Owner

Originally created by @derekoharrow on GitHub (Apr 29, 2022).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

The new MQTT monitor feature is great, but is a little basic. You can only match a topic with a set value. Often in MQTT the topic can consist of many values in JSON format. It would be great to be able to match just one of these values rather than the whole topic, and other values may change, but the service may still be up.

It would also be great if you could match using multiple values - e.g. "running" OR "healthy" both meaning up whereas "stopped", "exited", etc. would mean down.

✔️ Solution

As above.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @derekoharrow on GitHub (Apr 29, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description The new MQTT monitor feature is great, but is a little basic. You can only match a topic with a set value. Often in MQTT the topic can consist of many values in JSON format. It would be great to be able to match just one of these values rather than the whole topic, and other values may change, but the service may still be up. It would also be great if you could match using multiple values - e.g. "running" OR "healthy" both meaning up whereas "stopped", "exited", etc. would mean down. ### ✔️ Solution As above. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:08:18 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:08:24 -05:00

Author

Owner

@mrMiimo commented on GitHub (Sep 26, 2022):

yea, this could be the turning point for this type of monitoring

@mrMiimo commented on GitHub (Sep 26, 2022): yea, this could be the turning point for this type of monitoring

deekerman commented

2026-02-28 02:08:24 -05:00

Author

Owner

@johntdyer commented on GitHub (Dec 15, 2022):

I think JSON path support for all check responses would be a nice add, or at the very least regex... better yet json path on key, and regex on value :)

@johntdyer commented on GitHub (Dec 15, 2022): I think JSON path support for all check responses would be a nice add, or at the very least regex... better yet json path on key, and regex on value :)

deekerman commented

2026-02-28 02:08:24 -05:00

Author

Owner

@alexmaurer-madis commented on GitHub (Dec 17, 2022):

I think JSON path support for all check responses would be a nice add, or at the very least regex... better yet json path on key, and regex on value :)

I think like you that JSON and REGEX is a must have feature to check responses.

I agree that, ideally, this must be possible for all responses (no matter the monitor).

REGEX was proposed in issue #2405

But when you have, in the same response, multiple JSON key-value pairs or array to check the easiest way for me would be to be able to write code of Javascript like the function node in node-red.

I opened a feature-request 2431

@alexmaurer-madis commented on GitHub (Dec 17, 2022): > I think JSON path support for all check responses would be a nice add, or at the very least regex... better yet json path on key, and regex on value :) I think like you that JSON and REGEX is a must have feature to check responses. I agree that, ideally, this must be possible for all responses (no matter the monitor). * REGEX was proposed in [issue #2405](https://github.com/louislam/uptime-kuma/issues/2405) But when you have, in the same response, **multiple JSON key-value pairs or array to check** the easiest way for me would be to be able to write code of Javascript like the [function node](https://nodered.org/docs/user-guide/nodes#function) in node-red. I opened a [feature-request 2431](https://github.com/louislam/uptime-kuma/issues/2431)