fix(explorer): clarify cloud support and point to the Admin UI - #7629
Open
jstirnaman wants to merge 3 commits into
Open
fix(explorer): clarify cloud support and point to the Admin UI#7629jstirnaman wants to merge 3 commits into
jstirnaman wants to merge 3 commits into
Conversation
Explorer docs described Cloud Serverless, Cloud Dedicated, and Clustered support as coming "in a future release" while the get started guide listed Serverless and Dedicated as supported in query mode, leaving customers with the impression that Explorer is a supported way to work with Cloud Dedicated. Cloud Dedicated and InfluxDB 3 Cloud customers should administer their clusters and instances through the Admin UI at console.influxdata.com. - Replace the outdated "future release" statement in About Explorer with a Product support section that states current support levels. - Convert the supported products list in the Explorer get started guide to a table that distinguishes "query and administer" from "query only". - Add callouts in the Explorer docs directing Cloud Dedicated and InfluxDB 3 Cloud users to the Admin UI for administrative tasks. - Add a callout to Administer InfluxDB Cloud Dedicated and to the Cloud Dedicated get started guide advising the Admin UI or influxctl over the standalone Explorer UI. These state the directive only; they make no claim about what Explorer can do against a cluster, which needs verification. - Add an equivalent callout to the shared InfluxDB 3 admin index, scoped with show-in so it renders only for InfluxDB 3 Cloud and not for Core or Enterprise, where Explorer is the recommended UI. - Fix broken #run-in-query-or-admin-mode anchors in the Explorer manage databases and manage tokens pages. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MgQ2tqMK4FPgn4WnYDdkEt
Contributor
Vale Style Check Results
Warnings (4)
✅ Check passed |
github-actions
Bot
added
product:explorer
Contributor
🔗 Link Check Results — Link Check Bot✅ All links are valid
|
| Source File | URL | Issue |
|---|---|---|
content/influxdb3/cloud-dedicated/admin/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/cloud-dedicated/get-started/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/cloud-dedicated/get-started/_index.md |
file:///home/runner/work/docs-v2/docs-v2/public/influxdb3/cloud-dedicated/api/management | File not found. Check if file exists and path is correct: File not found. Check … |
content/influxdb3/cloud/admin/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/core/admin/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/enterprise/admin/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/explorer/about/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/explorer/get-started/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/explorer/manage-databases/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/explorer/manage-tokens/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
Full details: workflow run summary and artifact. Last updated: 2026-08-07 21:29:29 UTC
Contributor
📦 PR Preview — Preview Bot
Changed pages (9)Preview auto-deploys on push. Will be cleaned up when PR closes. |
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies Explorer support and directs cloud administrators to the Admin UI.
Changes:
- Adds an Explorer product-support matrix.
- Adds cloud administration guidance.
- Corrects two operational-mode anchors.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
content/shared/influxdb3-admin/_index.md |
Adds Cloud Admin UI guidance. |
content/influxdb3/explorer/manage-tokens.md |
Corrects the operational-mode anchor. |
content/influxdb3/explorer/manage-databases.md |
Corrects the operational-mode anchor. |
content/influxdb3/explorer/get-started.md |
Adds support levels and cloud guidance. |
content/influxdb3/explorer/about/_index.md |
Documents current product support. |
content/influxdb3/cloud-dedicated/get-started/_index.md |
Recommends supported administration tools. |
content/influxdb3/cloud-dedicated/admin/_index.md |
Directs administrators away from Explorer. |
…brary anchor Address review feedback on the Explorer and Admin UI callouts. The InfluxDB 3 Cloud callout listed databases, tables, tokens, and users as Admin UI tasks. That enumeration is documented for Cloud Dedicated, whose Admin UI sidebar lists those resources, but it contradicts the InfluxDB 3 Cloud docs: content/influxdb3/cloud/admin/tokens/_index.md says to manage tokens with the influxdb3 CLI or the HTTP API, and the Cloud Admin UI page covers users only. Make the Explorer and shared admin callouts recommendation-only so they don't present unconfirmed console capabilities as settled. Also fix a pre-existing broken anchor in the Cloud Dedicated get started tools table. The table linked to #influxdb-3-client-libraries, but the heading is "InfluxDB client libraries" (#influxdb-client-libraries), which covers both v3 and v2 client libraries. The link, not the heading, was wrong. This link is unchanged on master; the link checker only began scanning the file because this branch modifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MgQ2tqMK4FPgn4WnYDdkEt
Contributor
Author
|
Pushed c5c6174, which addresses the link-check failure and all three review comments. Review comments — all three acceptedThe review was right, and one comment caught a real defect. I had written "use the Admin UI to manage databases, tables, tokens, and users" for both Cloud Dedicated and InfluxDB 3 Cloud. That enumeration is grounded for Dedicated —
So the callout contradicted the product's own docs. Fixed by making the callouts recommendation-only:
The Cloud Dedicated get-started callout keeps its enumeration, since that one is documented. Link check
This anchor is unchanged on master; my diff never touched that line. The link checker only started scanning the file because this branch modifies it, which surfaced a latent break. The identical mismatch exists at Vale0 errors. The 4 warnings are pre-existing and untouched by this branch: the three Generated by Claude Code |
Admin functionality belongs in the admin sections, not duplicated in callouts or the get started tools table. Enumerating resources also misleads by omission: an admin section whose children are CLI and API pages reads as though the Admin UI doesn't support those tasks. Reduce every callout to the one durable point -- prefer the Admin UI over the standalone Explorer UI -- and let the admin sections state which interface to use for each task. - Drop "manage databases, tables, tokens, and users" from the Cloud Dedicated get started callout; link to the admin section instead. - Drop the influxctl reference from the Cloud Dedicated admin callout. - Drop "and the tools described in the following articles" from the shared InfluxDB 3 Cloud callout. - Shorten the Explorer pointers to "For administrative tasks, see ...". The tools comparison table still carries no Admin UI row. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MgQ2tqMK4FPgn4WnYDdkEt
sanderson
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related: #7626, #7627, #7628 (follow-ups, not closed by this PR)
What changed
Explorer docs no longer imply that InfluxDB 3 Explorer is a supported way to work with InfluxDB Cloud Dedicated, and the Cloud Dedicated and InfluxDB 3 Cloud docs now point administrators to the Admin UI at console.influxdata.com.
show-inso it renders only for that product.#run-in-query-or-admin-mode, an anchor that does not exist. The heading on the install page is "Choose operational mode".#influxdb-3-client-libraries, but the heading is "InfluxDB client libraries" and covers both v3 and v2 client libraries, so the link was wrong rather than the heading. Unchanged on master; the link checker only began scanning the file because this branch modifies it.Why
A customer was told they could "technically use" Explorer with Cloud Dedicated. Explorer has only partial support for Dedicated, and Dedicated customers should be using the Admin UI.
The docs invited that mistake by contradicting themselves. About Explorer said support for Serverless, Dedicated, and Clustered was coming "in a future release", while the get started guide already listed Serverless and Dedicated as supported in query mode. Neither page mentioned the Admin UI.
Impact
Cloud Dedicated and InfluxDB 3 Cloud readers are now directed to the console for administrative tasks. Core and Enterprise guidance is unchanged — Explorer is still the recommended UI for those products, and the new shared-content callout is scoped so it never appears on their pages.
The callouts state a preference and nothing more. They don't enumerate which resources the Admin UI manages, and they make no claim about what Explorer can do against a cluster. Two reasons:
Which interface to use for each task belongs on the specific admin pages, where it can be stated with the detail it needs.
For the same reason, no Admin UI row was added to the Cloud Dedicated tools comparison table.
Verification
npx hugo --quietpasses.content/shared/influxdb3-admin/_index.mdis sourced by Core, Enterprise, and InfluxDB 3 Cloud. An unscoped callout would tell Core and Enterprise users to avoid Explorer, which is the opposite of the guidance for those products. Confirmed in the built output that the callout appears on/influxdb3/cloud/admin/and on neither/influxdb3/core/admin/nor/influxdb3/enterprise/admin/. A site-wide search finds it on exactly two pages: Cloud and Cloud Dedicated.version: cloudis not globally unique —influxdb_cloud(Cloud TSM) cascades the same value. It is unambiguous here only because Cloud TSM doesn't source this file, which is why the scoping is verified by build output rather than assumed. Tracked in InfluxDB 3 Cloud has no identify-version page, blocked byversion: cloudkey collision #7627.#choose-operational-modeand#influxdb-client-librariesanchors.cloud-dedicatedconfigs.Checklist
npx hugo --quiet)Suggested reviewers (click to expand)
Based on files changed:
/content/shared/Product review is worth having here: the support levels this PR documents came from a support thread, and the open questions in #7628 are what kept further capability claims out of the diff.