anchor.diff:      - mod-gearman/*
   ----
   
  -To execute the Ansible playbook at the startup, we mount the folder `ansible_dropin` into to omd container. This is done by the following [Docker Compose] file:
  +To execute the Ansible playbook at the startup, we mount the folder `ansible_dropin` into `root/ansible_dropin` at the omd container. This is done by the following [Docker Compose] file:
   
   .link:part_02/omd-nagios/docker-compose.yml[`part_02/omd-nagios/docker-compose.yml`]
   [source,yaml]
  
positive.code: * Testing HTML content
  * Testing native UI content
  * Setting up a monitoring with:
  * Graphs about the performance times
  * Alerts on errors with screenshots
  * Continuous execution of the test suite in a loop
  
  
negative.code: 
  NOTE: To stop the loop press `CTRL + C`.
  
  After a few runs we should be able the the some graphs. Therefore click on the *Extra Action* button and a Grafana dashboard should appear.
  image:.pics/omd_extra_action.png[omd extra action]
  To get better view of the latest results choose `Last 15 minutes` as time interval.
  image:.pics/omd_graph_ok.png[omd graph ok]
  
  The red/yellow lines are representing the critical/warning times from the suite respectively the test case definition of <<part1>>. If one of the threshold is exceeded the service will change state to `WARNING` or `CRITICAL` and trigger a notification. To enable E-Mail notification, see https://labs.consol.de/de/omd/notifications.html[OMD Notifications].
  
  === Simulate an Error
  
  To get a feeling how Sakuli reacts on errors we will modify the testcase definition `sakuli_demo.js` to a not present link validation and force an error through this:
  
  .link:part_02/sakuli-tests/example_xfce/case1/sakuli_demo.js[`part_02/sakuli-tests/example_xfce/case1/sakuli_demo.js`]
  [soruce,js]
  