Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AppEx AI] Integrate pre-configured Kibana AI Connector to the O11y and Search GenAI powered functionality #202626

Closed
YulNaumenko opened this issue Dec 3, 2024 · 3 comments
Labels
8.18 candidate Team:Observability Team label for Observability Team (for things that are handled across all of observability) v8.18.0

Comments

@YulNaumenko
Copy link
Contributor

Currently solutions AI Assistants are using three different GenAI connector types, which helps to integrate directly with OpenAI, Gemini and Bedrock.
The long term vision is to migrate from the explicit connectors implementation to the usage of the generic .inference connector type #189027, which is integrated with Elasticsearch Inference API. This connector supports multiple LLMs integrations (including OpenAI, Gemini, Bedrock and much more), but due to the big scope of the complete adoption and migration path to .inference connector, the scope was reduced to the MVP integration which includes the usage of the pre-configured connector with EIS service.

In 8.18 there is a plan to provide Elastic Default LLM experience, which will be exposed within Kibana .inference connector type.
Requirements:

@pgayvallet
Copy link
Contributor

Duplicate of #199082, probably?

Note that

add .inference pre-configured connector instance to the list of the available connectors instances and select/use it by default (if the connector selection was not changed)

Seems out of the scope for appex-ai-infra, that logic is living in the o11y assistant's code.

prohibit the create/edit/delete of the new .inference connector instances.

Not sure this is being relevant here, as it seems unrelated to supporting the inference connector?

@wayneseymour wayneseymour added the Team:Observability Team label for Observability Team (for things that are handled across all of observability) label Dec 13, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/unified-observability (Team:Observability)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 13, 2024
@YulNaumenko
Copy link
Contributor Author

Implemented by #199082

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.18 candidate Team:Observability Team label for Observability Team (for things that are handled across all of observability) v8.18.0
Projects
None yet
Development

No branches or pull requests

4 participants