Skip to content

[Internal]: Add a known issue about connector selection to the Obs AI Assistant docs #2088

@viduni94

Description

@viduni94

Description

The LLM connector selection happens in a specific manner in the Obs AI Assistant. The exact behaviour is outlined in this document - https://docs.google.com/document/d/1-Sp0CUfdVFByYvtPNU2oHt2h3h6P47Uio8u9rIjPpwg/edit?usp=sharing

With the release of the Elastic Managed LLM, there is a chance for some users, this will end up being the default connector for their conversations because of the existing connector selection logic. Since this can appear as a surprise to the user, this needs to be documented under Known Issues until there is a way to set a default LLM connector.

The impacted customer group would be:

If the user HAD NOT previously made a specific connector selection for any of the following reasons:

  • They only had one connector available and it was always automatically picked for their conversations
  • They had multiple connectors available but didn’t make a specific selection and used the automatically picked connector for their conversations
  • They had previously selected a connector but cleared browser local storage or switched browsers/devices

AND all their existing connector names alphabetically sort BELOW “Elastic Managed LLM connector”, the automatically picked connector for their conversations will be the Elastic Managed LLM connector.

Resources

LLM connector selection - https://docs.google.com/document/d/1-Sp0CUfdVFByYvtPNU2oHt2h3h6P47Uio8u9rIjPpwg/edit?usp=sharing

Which documentation set does this change impact?

Elastic Cloud (Hosted and Serverless) only

Feature differences

None

What release is this request related to?

8.18

Serverless release

It's already available

Collaboration model

The documentation team

Point of contact.

Main contact: @viduni94

Stakeholders: @elastic/obs-ai-assistant

Metadata

Metadata

Assignees

Labels

Team:ExperienceIssues owned by the Experience Docs Team

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions