anchor.diff:  * Testing HTML content
   * Testing native UI content
   * Setting up a monitoring with:
  -* Graphs about the performance times
  +* Grafana graphs about the performance times (end user perspective)
   * Alerts on errors with screenshots
   * Continuous execution of the test suite in a loop
   
  
positive.code: omd-nagios    | AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 192.168.199.2. Set the 'ServerName' directive globally to suppress this message
  ----
  
  TIP: To shortcut some sepcial docker-compose commands, we can execute the script link:part_02/omd-nagios/deploy_omd.sh[`part_02/omd-nagios/deploy_omd.sh`] (ensures that containers remove and started fresh)
  
  After the sucessfull startup of the OMD we can now open the OMD Demo page and see two services `example_xfce_centos_chrome` and `example_xfce_centos_chrome`:
  
  1. Open https://localhost:8043/demo
  2. Accept the securtiy warning about the seflsigned certificate
  3. Login to OMD with user `omdadmin` and password `omd`
  image:.pics/omd_login.png[omd login]
  4. Click `Services` to get overview page
  image:.pics/omd_services.png[omd services]
  
  === Configure Sakuli tests
  
  After OMD is ready to receive results from Sakuli as passiv check, we need to configure the connection in our Sakuli tests:
  
  1) Add the created OMD network `omd-nagios` as external link to the `docker-compose.yml` of each sakuli test definition, so Sakuli can send data to the OMD server:
  
  
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]
  