From c41a4b9a08c185d02972a02a0866b24d127bd864 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 22 May 2026 16:55:03 +0000 Subject: [PATCH] docs(flaky-tests): document monitor category sections in UI The monitors page now groups monitors into two sections: Health classification (pass-on-retry, failure rate, failure count) and Lifecycle & performance (new-test, skipped-test, slow-test). This update reflects that organization in the Monitor Types section and explains the distinction between monitors that affect health status versus those that only apply labels. Source: trunk-io/trunk2#4010 (stack of #3991, #3992, #3993) Co-Authored-By: Claude --- flaky-tests/detection/index.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/flaky-tests/detection/index.mdx b/flaky-tests/detection/index.mdx index 9bca038..1debe8c 100644 --- a/flaky-tests/detection/index.mdx +++ b/flaky-tests/detection/index.mdx @@ -28,6 +28,13 @@ For example, if you have a broken failure rate monitor and a flaky pass-on-retry ## Monitor Types +Trunk groups monitors into two categories based on what they do when they activate: + +- **Health classification monitors** determine a test's overall health status (healthy, flaky, or broken). When one activates, the test's status changes across the dashboard, CI annotations, and notifications. +- **Lifecycle and performance monitors** apply labels to tests based on lifecycle events or performance characteristics. They do not affect health status. These monitors appear in a separate section of the monitors page. + +### Health Classification Monitors + | Monitor | What it detects | Available actions | Plan availability | Default state | |---|---|---|---|---| | [**Pass-on-Retry**](./pass-on-retry-monitor) | A test fails then passes on the same commit (retry after failure) | Classify (flaky) or [apply labels](../management/test-labels#automatic-labeling-from-monitors) | Team and above | Enabled |