Ask AI group filters #6529
Open
Ask AI group filters #6529
Conversation
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
This was
linked to
issues
Nov 10, 2025
Contributor
Author
|
I'm still working on some changes to help specify the InfluxDB version and clean up the text. |
sanderson
approved these changes
Nov 10, 2025
- 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
jstirnaman
force-pushed
the
jts-askai-group-filters
branch
from
6a52dc2 to
db06cd7
Compare
Use human-readable product names instead of URL paths for better UX. Example: 'My version: InfluxDB 3 Core' instead of '[version: /influxdb3/core/]'
jstirnaman
force-pushed
the
jts-askai-group-filters
branch
from
5dc5a4f to
813f83f
Compare
- 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
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.
- 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.
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.
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.
… files (i.e., test contains all the URLs it needs)
…roducts.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
- 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
- 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)
jstirnaman
force-pushed
the
jts-askai-group-filters
branch
from
2d412e5 to
0a9a697
Compare
- 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
jstirnaman
force-pushed
the
jts-askai-group-filters
branch
from
0a9a697 to
3289052
Compare
…"Viewing <product>" in disclaimer note.
jstirnaman
force-pushed
the
jts-askai-group-filters
branch
from
3289052 to
2d412e5
Compare
jstirnaman
force-pushed
the
jts-askai-group-filters
branch
from
12bd32a to
90fc81b
Compare
garylfowler
approved these changes
Nov 18, 2025
Contributor
garylfowler
left a comment
garylfowler
left a comment
There was a problem hiding this comment.
Great improvement, thanks!
sanderson
approved these changes
Nov 18, 2025
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.
/platform, and product/version-specific instructions under each version (https://test2.docs.influxdata.com/influxdb3/enterprise/admin/identify-version/)