Werk #18921: Check HTTP web service: Fix and improve text searches
| Component | Checks & agents | ||||
| Title | Check HTTP web service: Fix and improve text searches | ||||
| Date | Dec 8, 2025 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Incompatible - Manual interaction might be required | ||||
| Checkmk versions & editions |
|
This Werk contains the fixes as applied to Checkmk 2.3 with Werk #18922, but goes beyond that and improves the configuration and output of the Search for strings option.
Inverted header regex search didn't work
Like in Werk #18922, the inverted header regex search is fixed now.
New info text
Instead of (matched)/(not matched), the check output of regex searches now reads (match found)/(no match found).
This little difference better matches the expression about what is matched/not matched (The regex? Or the condition?)
And yes, like in Werk #18922, the output now is correct, with the following possibilities:
- OK Expected ... (match found)
- CRIT Expected (no match found)
- OK Not expected ... (no match found)
- CRIT Not expected ... (match found)
Default CRIT state
Yes, we deliberately wrote CRIT in the section above.
Since the initial release of the new Check HTTP web service (check_httpv2) active check, we received some feedback regarding the (in)compatibility to the legacy Check HTTP service (check_http) active check in some parts.
One common issue was check_http returning CRIT in case of failed string searches, while check_httpv2 returns WARN.
Based on this feedback we now change the state to CRIT to make check_httpv2 more suitable as a drop-in-replacement for the legacy check_http.
Please note that this is considered an incompatible change, as it happens on patch release upgrade.
You did like the WARN state? Then the next item is for you.
Configurable state
We think that a returned WARN state better resembles the general Checkmk behavior in case of a failing string search. A CRIT state rather expresses a degraded system, like unreachable recources, or an exceeded limit indicating that some failure is imminent.
Because of this, we decided to make the state for failing Search for strings conditions configurable. As mentioned above, it defaults to CRIT, but is now configurable via the additional Service state for failing text search condition entry.