Skip to content

Conversation

@benironside
Copy link
Contributor

Fixes #3693 by updating our requirements sections for all three Assistant pages. This effort started out an emphasis on updating the information about which Kibana privileges are required, but I decided to revisit the whole requirements section.

So far I've only made changes to the AI Assistant for Obs and Search and the AI Assistant for Security pages because I don't know enough about Agent Builder requirements and I couldn't find any obviously applicable privs in the UI.

@benironside benironside self-assigned this Nov 18, 2025
@github-actions
Copy link

github-actions bot commented Nov 18, 2025

@benironside benironside marked this pull request as ready for review November 18, 2025 22:03
@benironside benironside requested a review from a team as a code owner November 18, 2025 22:03
Copy link
Contributor

@nastasha-solomon nastasha-solomon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Left some edits for your consideration.


- To run {{obs-ai-assistant}} on a self-hosted Elastic stack, you need an [appropriate license](https://www.elastic.co/subscriptions).

- An account with a third-party generative AI provider that preferably supports function calling. If your AI provider does not support function calling, you can configure [AI Assistant settings](../../solutions/observability/observability-ai-assistant.md#obs-ai-settings) to simulate function calling, but this might affect performance.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know function calling is something used in Observability that Security doesn't use. We may want to keep a note that recommends a model that supports function calling or to configure simulated function calling.

I would only think this wouldn't be necessary if all of the models we have connectors for support function calling. @viduni94 maybe you would have some insight into this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks. Curious to hear further input but sounds like adding a note makes sense.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reached out to Viduni directly

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After my conversation with Viduni, I don't think we need to add a note. Recent proprietary models all support function calling, and if the selected model doesn't support function calling, we use simulated function calling so assistant still works.

@benironside benironside enabled auto-merge (squash) November 19, 2025 22:07
@benironside benironside merged commit d36a973 into main Nov 19, 2025
6 of 7 checks passed
@benironside benironside deleted the 3693-AI-assistants-setup-privs branch November 19, 2025 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Internal]: Removed AI Assistant Settings privilege

5 participants