DOC-2746-Updated troubleshooting page and added reference to Log files page [3.6]

Author: Tushar-TG-14

modules/troubleshooting/pages/troubleshooting-guide.adoc

@@ -7,13 +7,14 @@ This troubleshooting guide is only up to date for v2.6 and below. +
 Additional guidance for v3.0+ is in development.
 ====
 
-== Introduction
+The Troubleshooting Guide teaches you how to monitor the status of your TigerGraph system, and when needed, find the log files in order to get a better understanding of why certain errors are occurring. This guide covers log file debugging for data loading and querying.
+
+For a overview of available log files, their locations, and what information they contain, please refer to the xref:troubleshooting:log-files.adoc#_available_log_files[Log Files] documentation page.
 
-The Troubleshooting Guide teaches you how to monitor the status of your TigerGraph system, and when needed, find the log files in order to get a better understanding of why certain errors are occurring. This section covers log file debugging for data loading and querying.
 
 == General
 
-Before any deeper investigation, always run these general system checks :
+Before any deeper investigation, always run these general system checks:
 
 [source,console]
 ----
@@ -31,36 +32,6 @@ $ grun all "date"      (Make sure the time across all nodes are synchronized
                         with time difference under 2 seconds. )
 ----
 
-=== Location of Log Files
-
-The following command reveals the location of the log files :
-
-[source,console]
-----
-gadmin log
-----
-
-You will be presented with a list of log files. The left side of the resulting file paths is the component for which the respective log file is logging information.
-The majority of the time, these files will contain what you are looking for. You may notice that there are multiple files for each TigerGraph component.
-
-[NOTE]
-====
-The .out file extension is for errors. +
-The .INFO file extension is for normal behaviors.
-====
-
-In order to diagnose an issue for a given component, you'll want to check the .out log file extension for that component.
-
-image::https://lh5.googleusercontent.com/6MnNakec5fKh5faCoWdZwfzprqXyguDZXt15nz0QAG1M3vW1t0nmwo7oYr3DgwVsgJoIEjub-5tSA81UtOQ-Ot-9m30zZ9Zr5tRG077dgfZ7KaE3tMMafUK63oi6fILQeM-kQw6fKqc[]
-
-Other log files that are not listed by the *`gadmin log`* command are those for Zookeeper and Kafka, which can be found here:
-
-[source,console]
-----
-zookeeper : ~/tigergraph/zk/zookeeper.out.*
-kafka     : ~/tigergraph/kafka/kafka.out
-----
-
 === Synchronize time across nodes in a cluster
 
 TigerGraph will experience a variety of issues if clocks across different nodes in a cluster are out of sync. If running `grun all "date"` shows that the clocks are out of sync, it is highly recommended that you install NTP implementations such as https://chrony.tuxfamily.org/index.html[`chrony`] or http://manpages.ubuntu.com/manpages/xenial/man8/systemd-timesyncd.service.8.html[`timesyncd`] to keep them in sync.