Add links to the new logging_and_debugging chapter

Signed-off-by: Fabian Hartung <[email protected]>

Author: FaHaGit

docs/source/getting_started.rst

@@ -238,7 +238,8 @@ Before we start the first charging session, we shall open the EVerest log to mon
 process. The EVerest log is stored in the systemd journal and can be accessed via the journalctl
 command. The journalctl command provides a lot of options to filter the log messages. 
 Now just type "journalctl -f -u everest -n 50" to see the last 50 log messages of the EVerest
-charging stack and to follow the charging process in real time.
+charging stack and to follow the charging process in real time. For more information about the
+EVerest log, see the :ref:`logging_and_debugging` chapter.
 
 The EVerest log should look like this:
 

includes/troubleshooting_contact.inc

@@ -14,6 +14,11 @@ Do you have general questions about EVerest, please use the EVerest community's
 Do you have questions about the chargebyte BSP (incl. Yocto), please use
 `our support desk <https://chargebyte.atlassian.net/servicedesk/customer/portal/13>`_.
 
+.. note::
+    Before submitting a support request, make sure that all relevant log files have been captured.
+    The chapter :ref:`logging_and_debugging` describes the debugging options EVerest offers and shows
+    which logs are relevant for the respective case.
+
 Address
 ^^^^^^^