anchor.diff:  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`
  +TIP: To shortcut some special docker-compose commands, you can execute the script link:part_02/omd-nagios/deploy_omd.sh[`part_02/omd-nagios/deploy_omd.sh`] (ensures that containers will be removed and started from scratch)
  +
  +After the successful 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 security warning about the self-signed 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
  +
  +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:
  +After OMD is ready to receive results from Sakuli as passive check, we need to configure the connection in our Sakuli tests to froward the test results to OMD:
   
   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:
   
  
positive.code: 
  [[part2]]
  == Part 2
  //TODO TS read for correction
  
  In the second part of the tutorial, we will send the gathered results to a containerized https://labs.consol.de/de/omd/index.html[OMD Labs] monitoring server.
  
  
negative.code:     ...
  ----
  
  On the next test run in the loop the OMD sever will change the state to `CRITICAL` and shows the error message:
  
      [CRIT] Sakuli suite "example_xfce_centos_chrome" (25.23s) EXCEPTION: 'CASE "case1": STEP "Test_Sahi_landing_page": _highlight(_link("XXXX_Logs")): TypeError:
  
  To get a idea about what happens, Sakuli automatically creates a screenshot of every error and append it to the service result:
  image:.pics/omd_error.png[omd error]
  
  With the updated Grafana template (version 1.1.0) it is even possible to see the screenshot directly in the Grafana graph, if you hoover over the purple annotation:
  image:.pics/omd_error_grafana.png[omd error grafana]
  
  
  == Conclusion
  
  The above tutorial shows how easy it is to setup a fully functional end-to-end monitoring with Sakuli, OMD and Docker. Sometime this use case is also called "application monitoring", but however Sakuli will no detect if an application is down, has functional errors or even have a performance issue.
  
  After all is set up, the example test cases can now be used as template for your own e2e tests and monitoring environment. With the release `1.1.0` it's also possible to run the whole setup in container management solutions like https://kubernetes.io[Kubernetes] or https://openshift.io/[OpenShift]. To get more information about this or about how to write your own e2e tests take a look to our official http://consol.github.io/sakuli/latest/index.html[Sakuli Documentation].
  
  If you need help or you have some further questions feel free to contact us through `sakuli@consol.de` or open an issue at Github: https://github.com/ConSol/sakuli-examples/issues/new[github.com/sakuli-examples/issues].
  
  
  
  