[auto-build] docs/troubleshooting-logs-link -> master

_docs/master/configuring-metabase/log-configuration.md

@@ -18,7 +18,7 @@ Metabase logs quite a bit of information by default. Metabase uses [Log4j 2](htt
 
 ## View and download Metabase logs
 
-You can find Metabase logs in **Admin settings** > **Troubleshooting** > **Logs**. You can filter the logs by keywords (for example, "sync") and download them as a text file.
+You can find Metabase logs in **Admin settings** > **Tools** > **Logs**. You can filter the logs by keywords (for example, "sync") and download them as a text file.
 
 If you're running self-hosted Metabase, you'll also be able see the logs in the terminal.
 
@@ -32,7 +32,7 @@ Metabase uses [log4j](https://logging.apache.org/log4j/2.x/)for logging configur
 
 ### Temporary override logging configuration
 
-To temporarily adjust the logging configuration, go to **Admin settings** > **Troubleshooting** > **Logs** and click on **Customize log levels**.
+To temporarily adjust the logging configuration, go to **Admin settings** > **Tools** > **Logs** and click on **Customize log levels**.
 
 You can select from log level presets for common troubleshooting tasks (for example, troubleshooting sync issues), or provide your own configuration as a JSON. For example, here's an override configuration that increases logging for troubleshooting linked filters:
 

_docs/master/installation-and-operation/running-metabase-on-azure.md

@@ -172,7 +172,7 @@ Change the version of the container to the new version in the **Full Image Name
 
 Visit your web app in Azure, and navigate to **Monitoring -> Log stream**.
 
-You should be able to see the logs as well inside Metabase by going to Settings -> Admin -> Troubleshooting -> Logs.
+You should be able to see the logs as well inside Metabase by going to Settings -> Admin -> Tools -> Logs.
 
 ### Performance tuning
 

_docs/master/troubleshooting-guide/cant-send-email.md

@@ -27,7 +27,7 @@ Before any other troubleshooting, try sending a test email to isolate the proble
 2. Confirm that your host, port, email address, and password are entered correctly. If they are, click **Save changes**. If your changes have successfully saved, you'll see an option to **Send test email**.
 3. Click **Send test email**. The test email will go the address associated with your Metabase account.
 4. Verify that the email is delivered to your account.
-5. If the message is not sent or an error message is displayed in Metabase, try to use the same account credentials in another email program and see if they work. See the logs for more detailed error by navigating to **Troubleshooting** and click **Logs** in the left sidebar.
+5. If the message is not sent or an error message is displayed in Metabase, try to use the same account credentials in another email program and see if they work. See the logs for more detailed error by navigating to **Tools** and click **Logs** in the left sidebar.
 
 ## Is the mail server actually sending the message?
 

_docs/master/troubleshooting-guide/db-connection.md

@@ -25,7 +25,7 @@ If your database connection is successful, but the tables aren't showing up in t
 
    - If Metabase is taking a long time to sync, go to [Troubleshooting syncs and scans](./sync-fingerprint-scan).
 
-2. Go to **Admin** > **Troubleshooting** > **Logs** to check if Metabase failed to sync [due to an error](#common-database-connection-errors).
+2. Go to **Admin** > **Tools** > **Logs** to check if Metabase failed to sync [due to an error](#common-database-connection-errors).
 
    - If the logs feel overwhelming, check out [How to read the server logs](./server-logs).
 
@@ -59,7 +59,7 @@ If you see this error message in the Metabase interface, go to [Troubleshooting
 
 ### Connections cannot be acquired from the underlying database
 
-If you see this error messages in the [logs](./server-logs) (**Admin** > **Troubleshooting** > **Logs**):
+If you see this error messages in the [logs](./server-logs) (**Admin** > **Tools** > **Logs**):
 
 1. Go to **Admin** > **Databases** and select your database.
 2. Go to **Advanced options** > **Additional JDBC connection string options** and add `trustServerCertificate=true`.

_docs/master/troubleshooting-guide/diagnostic-info.md

@@ -30,7 +30,7 @@ What data Metabase captures depends on the page you're on when you request diagn
 
 Metabase will log errors, both on the server and in the browser console, depending on where the error occurs, which can help you track down an issue. Administrators will have access to the server logs, and everyone with a browser can open the developer tools to see the console logs.
 
-**Accessing the Metabase server logs**: You can look for the logs that Metabase leaves on the server's file system (or wherever else you collect logs). If you're logged into Metabase with an Admin account, you can also access the logs by going to the top right of the screen and clicking on the **gear** icon > **Admin settings** > **Troubleshooting** > **Logs**. Check out [How to read the server logs](./server-logs)
+**Accessing the Metabase server logs**: You can look for the logs that Metabase leaves on the server's file system (or wherever else you collect logs). If you're logged into Metabase with an Admin account, you can also access the logs by going to the top right of the screen and clicking on the **gear** icon > **Admin settings** > **Tools** > **Logs**. Check out [How to read the server logs](./server-logs)
 
 **Checking for Javascript console errors:** Metabase will send debugging information and errors to your browser's developer console. To open the developer console, follow the instructions for your web browser:
 

_docs/master/troubleshooting-guide/loading-from-h2.md

@@ -25,7 +25,7 @@ You've installed Metabase, but:
 
 **Steps to take:**
 
-1. To check what you're using as the app database, go to **Admin Panel**, open the **Troubleshooting** tab, scroll down to "Diagnostic Info", and look for the `application-database` key in the JSON it displays.
+1. To check what you're using as the app database, go to **Admin Panel**, open the **Tools** tab, scroll down to "Diagnostic Info", and look for the `application-database` key in the JSON it displays.
 2. See [Migrating from H2](../installation-and-operation/migrating-from-h2) for instructions on how to migrate to a more robust app database.
 
 ## Are you trying to migrate the application database from H2 to something else?

_docs/master/troubleshooting-guide/saml.md

@@ -21,7 +21,7 @@ Verify that the application you created in your IdP supports SAML. Sometimes oth
 
 ## Is the issuer or Entity ID correct?
 
-After filling out the authentication form with your identity provider, you're taken back to Metabase but it throws an error. To see the error, go to **Admin settings** > **Troubleshooting** > **Logs**. You'll see an error that says something like **Incorrect response <issuer\>**.
+After filling out the authentication form with your identity provider, you're taken back to Metabase but it throws an error. To see the error, go to **Admin settings** > **Tools** > **Logs**. You'll see an error that says something like **Incorrect response <issuer\>**.
 
 **Root cause**: Your issuer or Entity ID is incorrect.
 
@@ -36,7 +36,7 @@ After filling out the authentication form with your identity provider, you're ta
 
 ## Is the SAML identity provider certificate value correct?
 
-After filling out the authentication form with your identity provider, you go back to Metabase but it throws an error. Go to **Admin settings** > **Troubleshooting** > **Logs**. You'll see an error that says something like **Invalid assertion error <issuer\>**.
+After filling out the authentication form with your identity provider, you go back to Metabase but it throws an error. Go to **Admin settings** > **Tools** > **Logs**. You'll see an error that says something like **Invalid assertion error <issuer\>**.
 
 **Root cause**: The certificate value you entered is incorrect.
 

_docs/master/troubleshooting-guide/sync-fingerprint-scan.md

@@ -26,7 +26,7 @@ Once you've confirmed that you're looking at a non-cached view of your tables an
 ## Syncing
 
 1. Make sure your database driver is up to date.
-2. Go to **Admin** > **Troubleshooting** > **Logs** to check the status of the sync.
+2. Go to **Admin** > **Tools** > **Logs** to check the status of the sync.
 3. Run a query against your database from the Metabase SQL editor to check for database connection or database privilege errors that aren't listed in the logs:
 
    ```sql
@@ -73,7 +73,7 @@ If the [connection is failing](./db-connection) or the database privileges are w
 
 **Explanation**
 
-Metabase will try to unfold JSON and JSONB records during the sync process, which can take up a decent chunk of query execution time. If you have a lot of JSON records, try disabling the automatic unfolding option to pull the sync out of slow-motion. Remember that you can follow the status of the sync from **Admin** > **Troubleshooting** > **Logs**.
+Metabase will try to unfold JSON and JSONB records during the sync process, which can take up a decent chunk of query execution time. If you have a lot of JSON records, try disabling the automatic unfolding option to pull the sync out of slow-motion. Remember that you can follow the status of the sync from **Admin** > **Tools** > **Logs**.
 
 ## Scanning
 
@@ -82,11 +82,11 @@ Metabase will try to unfold JSON and JSONB records during the sync process, whic
 3. Go to the column you want to update, and click the **gear** icon.
 4. Click **Discard cached field values**.
 5. Click **Re-scan this field**.
-6. Go to **Admin** > **Troubleshooting** > **Logs** to follow the status of the scan and debug errors from there.
+6. Go to **Admin** > **Tools** > **Logs** to follow the status of the scan and debug errors from there.
 
 ### Special cases
 
-If you're waiting for the initial scan to run after connecting a database, make sure the initial sync has completed first (remember you can check the status from **Admin** > **Troubleshooting** > **Logs**).
+If you're waiting for the initial scan to run after connecting a database, make sure the initial sync has completed first (remember you can check the status from **Admin** > **Tools** > **Logs**).
 
 **Explanation**
 
@@ -126,7 +126,7 @@ To manually re-trigger a fingerprinting query for a given column:
 
 ### Special cases
 
-If you're waiting for the initial fingerprinting query to run after connecting a database, make sure the initial sync has completed first (remember you can check the status from **Admin** > **Troubleshooting** > **Logs**).
+If you're waiting for the initial fingerprinting query to run after connecting a database, make sure the initial sync has completed first (remember you can check the status from **Admin** > **Tools** > **Logs**).
 
 If you're using MongoDB, Metabase fingerprints the first 10,000 documents per collection. If you're not seeing all of your fields, it's because those fields might not exist in those first 10,000 documents. For more info, see our [MongoDB reference doc](../databases/connections/mongodb#i-added-fields-to-my-database-but-dont-see-them-in-metabase).