starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

[groups] Rules for combinations #2916

New issue

Closed

opened 2026-02-28 03:11:31 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:11:31 -05:00

Owner

Originally created by @superen7527 on GitHub (Dec 12, 2023).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

1 more matching rules

2 add matching combinationsat the moment,

✔️ Solution

1 There seems to be an issue with this already, but I would like to add regular expressions as conditions.

2 it seems thatcan only combine them in groups, but if can, I'd prefer to do it as a conditional statement in a monitor.

Stripped from https://github.com/louislam/uptime-kuma/issues/4013

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @superen7527 on GitHub (Dec 12, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description 1 more matching rules 2 add matching combinationsat the moment, ### ✔️ Solution 1 There seems to be an issue with this already, but I would like to add regular expressions as conditions. 2 it seems thatcan only combine them in groups, but if can, I'd prefer to do it as a conditional statement in a monitor. Stripped from https://github.com/louislam/uptime-kuma/issues/4013 ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:11:31 -05:00

closed this issue
added the
A:monitor

help
labels

deekerman commented

2026-02-28 03:11:37 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 12, 2023):

As stated in https://github.com/louislam/uptime-kuma/issues/4013

謝謝你的建議，一般來說，我們希望一個 Issue = 一個建議/問題/錯誤報告

The rationale behind this is quite simply that rewording issue titles/descriptions, assiging tags and other stuff related to managing issues is impossible otherwise.

I would like to add regular expressions as conditions

Currently these issues exist

I think you mean you would like REGEX as a general monioring option for all monitors that support checking content
"The current plan" to get this implemented is #3919 or a PR building on top of this.

add matching combinationsat the moment

it seems thatcan only combine them in groups, but if can, I'd prefer to do it as a conditional statement in a monitor.

Something was lost in translation here.

I think you are referring to either of these Issues:

=> as far as I read this, the second point is a duplicate.

@CommanderStorm commented on GitHub (Dec 12, 2023): As stated in https://github.com/louislam/uptime-kuma/issues/4013 > 謝謝你的建議，一般來說，我們希望一個 Issue = 一個建議/問題/錯誤報告 The rationale behind this is quite simply that rewording issue titles/descriptions, assiging tags and other stuff related to managing issues is impossible otherwise. > I would like to add regular expressions as conditions Currently these issues exist - https://github.com/louislam/uptime-kuma/issues/1851 - https://github.com/louislam/uptime-kuma/issues/2735 - https://github.com/louislam/uptime-kuma/issues/1938 I think you mean you would like REGEX as a general monioring option for all monitors that support checking content "The current plan" to get this implemented is #3919 or a PR building on top of this. > add matching combinationsat the moment > it seems thatcan only combine them in groups, but if can, I'd prefer to do it as a conditional statement in a monitor. Something was lost in translation here. I think you are referring to either of these Issues: - #2487 - #1089 - #3387 => as far as I read this, the second point is a duplicate.

deekerman commented

2026-02-28 03:11:37 -05:00

Author

Owner

@superen7527 commented on GitHub (Dec 19, 2023):

I think you mean you would like REGEX as a general monioring option for all monitors that support checking content

II can't understand this sentence. The effect I want to achieve is to enter a string similar to ^\s*(\S+)\s+(.+)\s*$ to match such as hh.donation.com localhost:8080/update a string like this in the http keyword.

The rationale behind this is quite simply that rewording issue titles/descriptions, assiging tags and other stuff related to managing issues is impossible otherwise.

I thought they were in the same category so put them together. I'm sorry I'm not a competent issue posting user. I don't know what to do with this issue anymore, all the issues I need to express have already been sent. I appreciate you doing the searching on my behalf. Then ownership of this issue is yours, you can merge and categorize and classify it or close it or keep it for updating to perfecting regular expressions, it's all up to you. I think I've created too many pointless issues, and I won't address any of them next with unprofessional behavior so that maybe I won't bother you guys again.

Very thankful for this project. I hope it gets better and better.

我以为是同一类就放在一起了。很抱歉我不是一个合格的发issue用户。我不知道怎么处理这个帖子了，我需要表达的issue已经都发出来了。很感谢你替我进行的搜索代劳。那么这个帖子的所有权交给你，你可以把它合并归类分类或者关闭，或者保留以更新到完善正则表达式，这些都由你处理。我想我已经制造太多的无意义issue，接下来我不会再以不专业的行为去处理任何一个issue了，这样或许就不会再次打扰到你们。

很感谢这个项目。希望越来越好。

@superen7527 commented on GitHub (Dec 19, 2023): > I think you mean you would like REGEX as a general monioring option for all monitors that support checking content II can't understand this sentence. The effect I want to achieve is to enter a string similar to `^\s*(\S+)\s+(.+)\s*$` to match such as `hh.donation.com localhost:8080/update` a string like this in the `http keyword`. *** > The rationale behind this is quite simply that rewording issue titles/descriptions, assiging tags and other stuff related to managing issues is impossible otherwise. I thought they were in the same category so put them together. I'm sorry I'm not a competent issue posting user. I don't know what to do with this issue anymore, all the issues I need to express have already been sent. **I appreciate you doing the searching on my behalf.** Then ownership of this issue is yours, you can merge and categorize and classify it or close it or keep it for updating to perfecting regular expressions, it's all up to you. I think I've created too many pointless issues, and I won't address any of them next with unprofessional behavior so that maybe I won't bother you guys again. Very thankful for this project. I hope it gets better and better. *** 我以为是同一类就放在一起了。很抱歉我不是一个合格的发issue用户。我不知道怎么处理这个帖子了，我需要表达的issue已经都发出来了。很感谢你替我进行的搜索代劳。那么这个帖子的所有权交给你，你可以把它合并归类分类或者关闭，或者保留以更新到完善正则表达式，这些都由你处理。我想我已经制造太多的无意义issue，接下来我不会再以不专业的行为去处理任何一个issue了，这样或许就不会再次打扰到你们。很感谢这个项目。希望越来越好。

deekerman commented

2026-02-28 03:11:37 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 20, 2023):

Closing as a duplicate as by discussion above

@CommanderStorm commented on GitHub (Dec 20, 2023): Closing as a duplicate as by discussion above