From f90d5103f26a847bb3591838d6afe0c8093d1459 Mon Sep 17 00:00:00 2001 From: shamoon <4887959+shamoon@users.noreply.github.com> Date: Mon, 13 Oct 2025 13:16:10 -0700 Subject: [PATCH] Update docs --- docs/configs/services.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/configs/services.md b/docs/configs/services.md index f816e646b..9ae24b15e 100644 --- a/docs/configs/services.md +++ b/docs/configs/services.md @@ -120,7 +120,7 @@ Each widget can optionally provide a list of which fields should be visible via ### Block Highlighting -Widgets can tint their metric blocks automatically based on rules defined alongside the service. Attach a `highlight` section to the widget configuration and map each block to one or more numeric or string rules using the field key (for example, `queued`, `lan_users`). +Widgets can tint their metric block text automatically based on rules defined alongside the service. Attach a `highlight` section to the widget configuration and map each block to one or more numeric or string rules using the field key (for example, `queued`, `lan_users`). ```yaml - Sonarr: @@ -150,6 +150,11 @@ Widgets can tint their metric blocks automatically based on rules defined alongs - level: good when: equals value: "All good" + status_code: + string: + - level: warn + when: regex + value: "^5\\d{2}$" ``` Supported numeric operators for the `when` property are `gt`, `gte`, `lt`, `lte`, `eq`, `ne`, `between`, and `outside`. String rules support `equals`, `includes`, `startsWith`, `endsWith`, and `regex`. Each rule can be inverted with `negate: true`, and string rules may pass `caseSensitive: true` or custom regex `flags`. The highlight engine does its best to coerce formatted values, but you will get the most reliable results when you pass plain numbers or strings into ``.