Explore the latest product updates and best practices at our hybrid Checkmk Conference #12 from June 16-18, 2026 – Register here

Check manual page of robotmk_marker_based_kpi

Robotmk Marker-Based KPI

Included in All Checkmk editions
Source Code License Proprietary
Supported Agents Windows

Provides information about the status of a Robotmk KPI.

Mapping of keyword status to monitoring state: - PASS: OK - FAIL: CRIT - NOT RUN/NOT SET/SKIP: STALE

Additionally, the service will go stale if: - the age of the rebot result is more than 2 times higher than the configured execution interval. The result is considered outdated then. - the parent test was skipped due to a 'robot:exit' tag.

If multiple keywords from the same test are marked with same marker, the service state is UNKNOWN.

If the keyword status is PASS, the service produces a metric measuring the keyword runtime. Thresholds are configurable.

Discovery

One service is created per marked keyword(s). The item is a combination of the Plan ID, the sub-suite names to which the test belongs, the test name and the value passed to the marker keyword (discover_as).

Note: Overlong Robot Framework test case names may lead to issues with RRD file creation, as the backend derives RRD file paths directly from service (containing the test case names) and metric names. This can exceed filesystem limits or result in invalid paths, causing missing metrics and graphs without visible UI feedback. The same limitation applies to the names of keywords monitored as KPIs and to the custom service item suffixes (discover_as). It is recommended to keep Robot Framework test case names, keyword names and custom service item suffixes reasonably short until this limitation is resolved in a future version.