<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Robotmk on Clear Solutions IT</title>
    <link>https://clear-solutions-it.com/tags/robotmk/</link>
    <description>Recent content in Robotmk on Clear Solutions IT</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>contact@clear-solutions-it.com (Andreas Müller)</managingEditor>
    <webMaster>contact@clear-solutions-it.com (Andreas Müller)</webMaster>
    <copyright>[Legal Notice | Impressum](/impressum/)</copyright>
    <lastBuildDate>Fri, 18 Sep 2026 14:03:10 +0200</lastBuildDate><atom:link href="https://clear-solutions-it.com/tags/robotmk/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Setting Up Checkmk Synthetic Monitoring (Robotmk) Step by Step</title>
      <link>https://clear-solutions-it.com/posts/2026-09-18_checkmk-synthetic-monitoring/</link>
      <pubDate>Fri, 18 Sep 2026 14:03:10 +0200</pubDate>
      <author>contact@clear-solutions-it.com (Andreas Müller)</author>
      <guid>https://clear-solutions-it.com/posts/2026-09-18_checkmk-synthetic-monitoring/</guid>
      <description>A walkthrough of Checkmk&amp;rsquo;s Robotmk-based synthetic monitoring: Managed Robots, the scheduler bakery rule, the root-deployment gotcha it&amp;rsquo;ll throw at you, and how to actually verify the test ran instead of waiting on the schedule.</description>
      
    </item>
    
    <item>
      <title>Running Playwright on Rocky Linux 10 for Robotmk Synthetic Monitoring</title>
      <link>https://clear-solutions-it.com/posts/2026-09-18_robotmk-playwright-rocky-linux-10/</link>
      <pubDate>Fri, 18 Sep 2026 14:02:29 +0200</pubDate>
      <author>contact@clear-solutions-it.com (Andreas Müller)</author>
      <guid>https://clear-solutions-it.com/posts/2026-09-18_robotmk-playwright-rocky-linux-10/</guid>
      <description>Playwright officially only supports Debian/Ubuntu. Here&amp;rsquo;s the RHEL/Rocky package mapping, the correct RCC conda.yaml post-install hook, and the holotree caching trap that makes a stale environment look like a passing build.</description>
      
    </item>
    
  </channel>
</rss>
