Ask AI: Improve knowledge of Flux relationship to versions and products

[jstirnaman]

Problems:

It shouldn't consider Flux as "new". InfluxDB 3 editions use SQL and InfluxQL.

• Example: Ask AI referred to Flux as "new" when comparing all products and versions

  Cited sources:

  • https://docs.influxdata.com/influxdb/v1/flux/flux-vs-influxql
  • https://docs.influxdata.com/influxdb/v1/concepts/crosswalk/#query-languages

It should be aware of the context that the conversation started in or use group filtering to override more general ("global") knowledge.

• Example: With Flux in the Global group, and the chat scoped to InfluxDB 3, a general Flux question originating at InfluxDB 3 doesn't indicate that Flux isn't supported.
• Example: With the chat originating from influxdb3/enterprise, filtered to the InfluxDB 3 group, and Flux in Global, the question "use flux with this version" returns a Flux answer with no indication that it doesn't work with Ent 3.

It should know how to translate a Flux question to a Processing Engine solution (e.g. using the Downsampling plugin) as well as SQL and InfluxQL functions.

• Add Flux function mappings to SQL and InfluxQL references
• Example: https://app.kapa.ai/720100f9-ce93-4305-88fd-5fcf71effad7/coverage-gaps/clusters/3be8401d-a2fb-4e33-9aa7-8c0eb5ab0685

[jstirnaman]

I assigned Flux to the v1 and v2 groups (removed from Global), which resulted in a qualifier question:

1. Launched chat from influxdb3/enterprise
2. Asked "Use Flux with this version?"
3. Response: "I'd be happy to help you understand Flux compatibility, but I need to know which version of InfluxDB you're asking about. The support for Flux varies significantly across different InfluxDB versions..."

This is an improvement, but still ignorant of the user's current URL/context.

I followed up with:
Q: "My documentation URL path is /influxdb3/enterprise/"
A: "Thank you for clarifying! Based on your documentation URL path /influxdb3/enterprise/, you're using InfluxDB 3 Enterprise."