Regex in keyword field

[BoyanBlagoev]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

I am using Uptime Kuma to check certain endpoints which consist of several strings of System: UP - if everything is fine and System:DOWN if system goes DOWN. Issue is that when I use the HTTP Keyword type monitoring and set the Keyword to UP - Uptime Kuma checks only the first occurrence of UP and never goes on into the string even though there might be a DOWN further down the json.

Can I use a REGEX into the Keyword field? Can you give me example how I can check for every occurrence of a certain word and not to stop on the first check?

Or another question - should I use it with Upside down mode and look for DOWN?

🐻 Uptime-Kuma Version

1.17.1

💻 Operating System and Arch

GCP App Engine

🌐 Browser

Google Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

16.14.2

[github-actions]

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

[JulianGro]

Still an issue.
Any time you have multiple statuses from one source, Uptime Kuma cannot handle it.

[github-actions]

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

[JulianGro]

😡

[woj-tek]

That would be very helpful to verify that the response is actually correct.

[CommanderStorm]

@BoyanBlagoev
the keyword field does currently not have this as an option.
Reasonable implementations would likely get accepted though.

@JulianGro
The reason this is getting closed is, that this is using help instead of feature-request => the wrong issue template

[CommanderStorm]

I think this is a duplicate of #2735 or #631 which are using the correct issue template and in gerneral have recieved more traction.
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

[JulianGro]

I agree that #2735 is a duplicate of this.

[github-actions]

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

[JulianGro]

https://blog.benwinding.com/github-stale-bots/

[CommanderStorm]

@JulianGro We resolve help issues after 3 month
They are also not being locked as in the article you posted

As mentioned above (which you agreed with) this issue is a duplicate of #2735
=> keeping it open does not serve a purpose

[CommanderStorm]

As reasoned above, we are going to track this in #2735
=> closing as duplicate (despite this being the earlier issue ^^)