* Initial plan
* Add v1.12.2 FUTURE LIMIT and PAST LIMIT callouts
Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>
* fix(v1): Remove patch from Enterprise v1 name
* fix(ent1): Remove version from `PAST LIMIT` and `FUTURE LIMIT` callout
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jstirnaman <212227+jstirnaman@users.noreply.github.com>
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
* feat(askai): add Kapa.ai source group filtering for InfluxDB v3
- Add ai_source_group_ids field to all InfluxDB v3 products in data/products.yml
- Add getProductSourceGroupIds() function to retrieve source group IDs from product data
- Enables filtered AI responses using Kapa source groups for documentation pages
- Follows existing pattern for dynamic product configuration
- Implement version-specific config support (__v1, __v2 suffixes)
- Append version hints to example questions for InfluxDB database products only
- Make example questions generic (remove product-specific names)
- Tools (Telegraf, Chronograf, Kapacitor, Flux, Explorer) display questions without version hints
- Pre-fills chat input with [version: /path/] for InfluxDB database products
- Users can easily edit or remove the pre-filled text
- Works for manual opens (Cmd+K) and programmatic opens
- Converts module to TypeScript
* refactor(ask-ai): change version format to 'My version: <product name>'
Use human-readable product names instead of URL paths for better UX.
Example: 'My version: InfluxDB 3 Core' instead of '[version: /influxdb3/core/]'
* fix(ask-ai): restore working Kapa.open() pre-fill implementation
- Replace textarea detection with direct Kapa.open() call
- Add Kapa preinitialization code
- Use click handler on .ask-ai-open button with capture phase
- Handle conversation reset event to re-fill version context
- Remove console logging for cleaner production code
* fix(ask-ai): remove parentheses from example questions for consistency
Make example question format match the pre-fill format:
- Before: 'question (My version: product)'
- After: 'question My version: product'
This ensures users don't think there's a difference between the two formats.
* fix(askai): add Explorer product mapping for Ask AI widget
- Add influxdb3_explorer mapping to getCurrentProductData()
- Add explorer context to getContext() function
- Ensures Explorer pages use correct ai_sample_questions from products.yml
- Reorder Explorer questions with 'install and run' first
This fixes the issue where Explorer Ask AI widget was showing wrong
example questions by properly loading the influxdb3_explorer config.
* test(page-context): add comprehensive e2e tests for product mappings
Add Cypress tests to validate page-context.js correctly identifies:
- Product context values for all InfluxDB products
- Product data from products.yml configuration
- Version information
- AI sample questions and source group IDs
- Placeholder host values
Tests cover:
- InfluxDB 3 (Core, Enterprise, Explorer, Cloud variants, Clustered)
- InfluxDB v2 and v1
- InfluxDB Cloud (TSM)
- Tools (Telegraf, Chronograf, Kapacitor, Flux)
Validates the fix for Explorer Ask AI showing correct example questions.
Related to #jts-askai-group-filters branch work.
* feat(test): add --no-mapping flag to e2e test runner
Allow running functionality tests without requiring content file paths.
The --no-mapping flag skips content-to-URL mapping, making it easier
to run tests that don't depend on specific content files.
Usage:
# With content mapping (for content-specific tests)
node run-e2e-specs.js content/influxdb3/core/_index.md
# Without content mapping (for functionality tests)
node run-e2e-specs.js --spec cypress/e2e/page-context.cy.js --no-mapping
Benefits:
- Simplifies running functionality tests like page-context.cy.js
- Reduces test startup time by skipping unnecessary file mapping
- Makes test commands clearer about their purpose
The page-context test was updated to work correctly with this flag.
* deps: update caniuse and related hook files
* test: Add a `--no-mapping` flag to run tests without specific content files (i.e., test contains all the URLs it needs)
* chore(ask-ai): Format example questions
* test(page-context): add comprehensive e2e tests for all products in products.yml
- Expanded test suite from 6 to 27 tests covering all products
- Added tests for InfluxDB 3 products (Explorer, Core, Enterprise, Cloud Serverless, Cloud Dedicated, Clustered)
- Added tests for InfluxDB v2 and Cloud (TSM)
- Added tests for InfluxDB v1 and Enterprise v1
- Added tests for other products (Telegraf, Chronograf, Kapacitor, Flux)
- Validates page mappings in page-context.js
- Validates AI sample questions configuration in products.yml
- All 27 tests passing
* fix(page-context): correct enterprise_influxdb URL pattern matching
- Changed pattern from /enterprise_v1/ to /enterprise_influxdb/
- Fixes Ask AI example questions not showing correctly for Enterprise v1
- Pattern now matches actual URL structure /enterprise_influxdb/v1/
- All 27 e2e tests passing
* test(page-context): add UI validation for Ask AI widget configuration
- Added 4 tests checking Kapa widget script data attributes
- Tests verify data-modal-example-questions contains correct product-specific questions
- Validates Explorer, Core, Enterprise, and Enterprise v1 configurations
- All 31 tests passing (27 existing + 4 new UI tests)
* feat(ask-ai): add help in Ask AI widget placeholder
- InfluxDB placeholder recommends specifying product and version
- Fix page-context.js to use products.influxdb_cloud instead of products.cloud
- Add UI tests verifying version-specific naming in Kapa widget script tags
* feat(ask-ai): Tailors placeholder for each version/product. Disables "Viewing <product>" in disclaimer note.
* chore: improve `hostname` documentation for HTTPS usage
Clarified hostname requirements for HTTPS in meta node configuration.
* Update content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md
---------
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
* chore(enterprise_influxdb): specify Enterprise v1 and remove new signup notes:
- Removes instructions for new signups at portal.influxdata (at Marketing's request)
- Uses Enterprise v1 in titles and descriptions
- Updates title metadata template to use InfluxDB Enterprise v1
- Updates products.yml to use InfluxDB Enterprise v1
- Removes unused enterprise-name/-link shortcodes
I chose InfluxDB Enterprise v1 over InfluxDB v1 Enterprise due to recent usage patterns and because it's compatible with uses like "InfluxDB Enterprise 1.11.x" without being redundant.
* Apply suggestion from @jstirnaman
* Apply suggestion from @jstirnaman
* Apply suggestion from @jstirnaman
Removed references to using JWT for HTTP authentication with LDAP (e.g. `[http] shared-secret` and user JWT tokens). JWT does not use LDAP for authentication, so you wouldn't be using LDAP if you use JWT authentication.
Left in references to enabling JWT authentication for meta nodes. While not necessary for LDAP, meta node authentication via JWT is recommended for all installations.
- Move feature flag configuration from Advanced section into Step 3 of installation
- Update terminology from "Grafana OSS" to "running Grafana locally" to include both OSS and Enterprise
- Consolidate "Using Grafana Cloud with local InfluxDB" guidance into single note with direct link
- Remove redundant Advanced configuration section
Changes apply to all Grafana documentation pages:
- InfluxDB 3 products (Core, Enterprise, Cloud Serverless, Cloud Dedicated, Clustered)
- InfluxDB v2 and Cloud TSM
- InfluxDB v1 OSS and Enterprise
The feature flag requirement is now integrated directly into the installation workflow,
making it more discoverable for users setting up Grafana locally.
- Combine separate 'Query' and 'Build visualizations' sections into unified 'Query and visualize data' section
- Convert h2 headings to h3 under new parent section
- Update TOC to reflect new heading hierarchy
- Ensure all fragment links work correctly
Add note to all Grafana integration pages about using Grafana Cloud
with local InfluxDB instances. The note recommends running Grafana
locally to avoid exposing databases to the internet, and provides
information about configuring Grafana Cloud private data sources
as an alternative.
Updated files:
- content/shared/v3-process-data/visualize/grafana.md
- content/shared/influxdb-v2/tools/grafana.md
- content/influxdb/v1/tools/grafana.md
- content/enterprise_influxdb/v1/tools/grafana.md
- Add InfluxDB version detector shortcode to all Grafana pages
- Add comprehensive alt_links to v2 and Cloud Grafana pages
- Include links to all InfluxDB versions (v1, enterprise_v1, v2, cloud, and all v3 products)
- Improve cross-product navigation for Grafana documentation
- Add v1.12.2 as first official v1.12.x release (2025-09-15)
- Include all v1.12.0 and v1.12.1 features since they weren't officially released
- Add v1.12.2-specific bug fix for SSH key usage
- Update latest patch version to 1.12.2 in products.yml
- Add reusable PR template for future v1.x releases
- Add span tag for backward compatibility with v1.12.x links
Closesinfluxdata/docs-v2#6381
- Closes influxdata/DAR/issues/534
- Contact Support for assistance
- Add risks and technical details to truncate-shard command
- Add cautions to rebalance guide
- Add planning guidance for future data in schema_and_data_layout
**Revert this commit for the v1.12 release**\
- Remove links from release notes to upcoming 1.12.x features
- Add callout to explain that v1.12 isn't yet available
**Keep this commit for the upcoming v1.12 release**
- Label upcoming features as v1.12.0+:
- Update configuration documentation for data nodes
- Update database management documentation
- Update influx_inspect tool documentation
- Update show-shards documentation
- Revert product version references to 1.11.8 in products.yml
Migrates v1 OSS and Enterprise sections from the DockerHub README into new pages in docs-v2.
- Add a new section page for Installing and running with Docker.o
1. Created main Docker installation page (docker.md) with:
- Complete Docker setup instructions for Enterprise clusters
- Environment variable configuration options
- Persistent storage examples
- Network setup guidance
- License key requirements using GitHub note callout syntax
2. Enhanced existing installation pages:
- Added Docker installation sections to both meta and data node installation
pages
- Updated the main installation index to include Docker as an option
3. Created Docker troubleshooting guide (docker-troubleshooting.md) with:
- Common Docker-specific issues and solutions
- Debugging commands and best practices
- Positioned next to the Docker installation guide
4. Added proper cross-references:
- Used related frontmatter to link Docker installation to troubleshooting
- Updated navigation and references throughout
The migration preserves all the essential Docker README content while
integrating it properly into the existing InfluxDB Enterprise v1 documentation
structure, following the project's style guidelines and conventions.
Copilot
Scott Anderson
Jason Stirnaman
Geoffrey Wossum
Gary Fowler
Scott Anderson
meelahme
Jason Stirnaman
Jamie Strandboge
mdevy-influxdata
WeblWabl