[WIP] Create separate PR for validation change

.ci/scripts/check-support-links.sh

@@ -0,0 +1,25 @@
+#!/bin/bash
+# Check for non-standard InfluxData support links
+# Standard link: https://support.influxdata.com (no trailing slash, no path)
+
+set -e
+
+EXIT_CODE=0
+
+echo "Checking for non-standard InfluxData support links..."
+
+# Find all markdown files with non-standard support.influxdata.com URLs
+# Check for URLs with paths (/s/contactsupport, /s/login, etc.)
+if grep -rn "https://support\.influxdata\.com/[^)\s]*" content --include="*.md" | grep -v "https://support\.influxdata\.com)"; then
+    echo ""
+    echo "ERROR: Found support.influxdata.com URLs with paths or trailing slashes."
+    echo "Please use the standard format: https://support.influxdata.com"
+    echo ""
+    EXIT_CODE=1
+fi
+
+if [ $EXIT_CODE -eq 0 ]; then
+    echo "✓ All support links use the standard format."
+fi
+
+exit $EXIT_CODE

.ci/vale/styles/InfluxDataDocs/SupportLink.yml

@@ -0,0 +1,13 @@
+extends: substitution
+message: "Use the standard InfluxData support link format: '%s'"
+link: "https://github.com/influxdata/docs-v2/blob/master/DOCS-CONTRIBUTING.md"
+level: error
+ignorecase: false
+nonword: true
+# Match support.influxdata.com URLs with paths or trailing slashes
+# and suggest the canonical form without them
+swap:
+  # Match any URL with /s/ path (login, contactsupport, etc.)
+  'https://support\.influxdata\.com/s/[^\)>\s]+': 'https://support.influxdata.com'
+  # Match base URL with trailing slash
+  'https://support\.influxdata\.com/': 'https://support.influxdata.com'

DOCS-CONTRIBUTING.md

@@ -164,6 +164,21 @@ Save images using the following naming format: `project/version-context-descript
 For example, `influxdb/2-0-visualizations-line-graph.png` or `influxdb/2-0-tasks-add-new.png`.
 Specify a version other than 2.0 only if the image is specific to that version.
 
+#### InfluxData Support links
+
+When linking to InfluxData Support, use the canonical URL without trailing slashes or paths:
+
+```markdown
+[contact InfluxData support](https://support.influxdata.com)
+```
+
+**Do not use**:
+- `https://support.influxdata.com/` (trailing slash)
+- `https://support.influxdata.com/s/contactsupport` (path)
+- `https://support.influxdata.com/s/login/?ec=302&startURL=%2Fs%2Fcontactsupport` (login redirect)
+
+The pre-commit hook will check for and reject non-standard support link formats.
+
 ### Essential Frontmatter Reference
 
 Every documentation page includes frontmatter which specifies information about the page.

content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-log.md

@@ -0,0 +1,149 @@
+---
+title: View the query log
+description: >
+  View and analyze queries executed on your cluster using the Admin UI Query History
+  or by querying the _internal database with influxctl.
+menu:
+  influxdb3_cloud_dedicated:
+    name: View the query log
+    parent: Troubleshoot and optimize queries
+weight: 351
+influxdb3/cloud-dedicated/tags: [query, observability, admin]
+related:
+  - /influxdb3/cloud-dedicated/reference/cli/influxctl/query/
+  - /influxdb3/cloud-dedicated/reference/admin-ui/
+  - /influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/system-information/
+---
+
+The query log records queries executed on your {{% product-name %}} cluster.
+Use it to monitor query performance, find slow-running queries, and troubleshoot failed executions.
+
+> [!Note]
+> #### Query logging is not enabled by default
+>
+> The query log is not enabled by default on all clusters as it can create a negligible ingest load on your cluster. 
+> To enable it for your cluster, [contact InfluxData support](https://support.influxdata.com).
+
+Use the Admin UI or the [`influxctl query` command](/influxdb3/cloud-dedicated/reference/cli/influxctl/query/) to view the query log.
+
+{{< tabs-wrapper >}}
+{{% tabs %}}
+[Admin UI](#)
+[influxctl](#)
+{{% /tabs %}}
+{{% tab-content %}}
+## Access the Cloud Dedicated Admin UI
+
+1. To access the {{% product-name %}} Admin UI, visit the following url in your browser:
+
+   <pre>
+   <a href="https://console.influxdata.com">https://console.influxdata.com</a>
+   </pre>
+
+2. Use the credentials provided by InfluxData to log into the Admin UI.
+   If you don't have login credentials, [contact InfluxData support](https://support.influxdata.com).
+
+3. Open the cluster you want to inspect and go to **Query History**.
+
+If query logging is enabled for your cluster, any admin user can access the query log in the Admin UI automatically; no database token is required.
+
+
+In Query History you can:
+
+- **Search** by Database Token ID to see queries run with a specific token.
+- **Filter** by:
+  - **Status** (for example, success, failure)
+  - **Database**
+  - **Query type** (for example, SQL, InfluxQL)
+  - **Source** (for example, User Queries, UI)
+  - **Time range** (for example, last 24 hours)
+
+The table lists each query with its status, query text, database, query type, duration, and timestamp.
+You can use the column headers to sort (for example by duration or time).
+
+
+<!-- vale Vale.Terms = NO -->
+{{< img-hd src="/img/influxdb3/cloud-dedicated-admin-ui-query-log-list-view.png" alt="Query History list view in the Admin UI with search, filters, and table" />}}
+
+
+
+You can also expand a row to see more details about that execution.
+
+
+<!-- vale Vale.Terms = NO -->
+{{< img-hd src="/img/influxdb3/cloud-dedicated-admin-ui-query-log-detail.png" alt="Query History detail view in the Admin UI" />}}
+
+{{% /tab-content %}}
+{{% tab-content %}}
+
+<!------------------------------- BEGIN INFLUXCTL ----------------------------->
+
+Use the [`influxctl query` command](/influxdb3/cloud-dedicated/reference/cli/influxctl/query/)
+to run SQL against the `_internal` database and `query_log` table.
+Query log entries are stored in the `_internal` database.
+
+1. If you haven't already, [download and install the `influxctl` CLI](/influxdb3/cloud-dedicated/reference/cli/influxctl/#download-and-install-influxctl), and then [configure an `influxctl` connection profile](/influxdb3/cloud-dedicated/reference/cli/influxctl/#configure-connection-profiles) for your cluster.
+2. [Create a database token](/influxdb3/cloud-dedicated/admin/tokens/database/create/?t=influxctl) that has read access to the `_internal` database.
+   Replace {{% code-placeholder-key %}}`DATABASE_TOKEN`{{% /code-placeholder-key %}} in the examples below with your token.
+3. Run the **query** subcommand with `--database` and `--language` (and optionally `--config`).
+   Global flags such as `--config` must come before the command; query flags such as `--database`, `--language`, and `--token` must come after `query`.
+
+{{% code-placeholders "DATABASE_TOKEN" %}}
+
+**List recent successful queries with compute duration above a threshold (for example, 0.6 ms):**
+
+```sh
+influxctl query \
+  --token DATABASE_TOKEN \
+  --database _internal \
+  --language sql \
+  'SELECT * FROM query_log WHERE success = '\''true'\'' AND compute_duration_ns > 600000 LIMIT 10'
+```
+
+
+**Filter by namespace (database) and time range:**
+
+```sh
+influxctl query \
+  --token DATABASE_TOKEN \
+  --database _internal \
+  --language sql \
+  'SELECT * FROM query_log WHERE namespace_name = '\''my_database'\'' AND time >= now() - INTERVAL '\''1 day'\'' LIMIT 50'
+```
+
+{{% /code-placeholders %}}
+
+**Example output:**
+
+```
+| auth_id        | compute_duration_ns | phase   | query_type | query_text                                              | success | time                    |
+|----------------|---------------------|---------|------------|---------------------------------------------------------|---------|--------------------------|
+| token-id-xxxx  |             2314333 | success | sql        | SELECT * FROM query_log WHERE success = 'true' AND ...  | true    | 2026-02-25T00:30:30Z     |
+| token-id-yyyy  |          3673637621 | success | sql        | SELECT * FROM my_measurement WHERE time > now() - ...  | true    | 2026-02-25T00:28:57Z     |
+| token-id-yyyy  |          1443145654 | success | sql        | SELECT COUNT(*) FROM query_log WHERE ...                | true    | 2026-02-25T00:29:02Z     |
++----------------+---------------------+---------+------------+---------------------------------------------------------+---------+--------------------------+
+```
+
+<!-------------------------------- END INFLUXCTL ------------------------------>
+{{% /tab-content %}}
+{{< /tabs-wrapper >}}
+
+## Query log data and columns
+
+The `query_log` table in `_internal` includes information such as:
+
+- **Status and phase**: `success`, `running`, `phase` (for example, received, planned, permit, success, fail, cancel).
+- **Identifiers**: `id`, `namespace_id`, `namespace_name`, `query_type` (for example, sql, influxql), `auth_id`, `trace_id`.
+- **Query content**: `query_text`, `query_params`.
+- **Timing**: `time` (timestamp), `query_issue_time_ns`, `permit_duration_ns`, `plan_duration_ns`, `execute_duration_ns`, `end_to_end_duration_ns`, `compute_duration_ns`.
+- **Resource usage**: `partition_count`, `parquet_file_count`, `max_memory_bytes`, and ingester-related fields.
+
+Durations are stored in nanoseconds (for example, `compute_duration_ns`, `execute_duration_ns`).
+
+
+> [!Note]
+> #### Use string literals for status columns
+>
+> In the `query_log` table, `success` and `running` are stored as strings (`'true'` or `'false'`), not booleans.
+> In SQL predicates, use string comparison—for example, `success = 'true'` or `running = 'false'`—to avoid type coercion errors.
+

lefthook.yml

@@ -22,6 +22,12 @@ pre-commit:
           echo "   Use 'python' instead of 'py' for code fences."
           errors=1
         fi
+        # Check for non-standard support.influxdata.com URLs
+        if grep -E 'https://support\.influxdata\.com/[^)\s]*' {staged_files} 2>/dev/null | grep -v 'https://support\.influxdata\.com)'; then
+          echo "❌ Found non-standard support.influxdata.com URL."
+          echo "   Use 'https://support.influxdata.com' (no trailing slash, no path)."
+          errors=1
+        fi
         exit $errors
       fail_text: "Deprecated markdown patterns found. See messages above for details."
     eslint-debug-check: