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

Ports #3975 to serverless #4293

Merged
merged 2 commits into from
Oct 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/en/serverless/ai-assistant/ai-assistant.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -247,7 +247,7 @@ You can continue a conversation from a contextual prompt by clicking **Start cha

### Add the AI Assistant connector to alerting workflows

You can use the Observability AI Assistant connector to add AI-generated insights and custom actions to your alerting workflows.
You can use the [Observability AI Assistant connector](((kibana-ref))/obs-ai-assistant-action-type.html) to add AI-generated insights and custom actions to your alerting workflows.
To do this:

1. <DocLink slug="/serverless/observability/create-manage-rules" text="Create (or edit) an alerting rule" /> and specify the conditions that must be met for the alert to fire.
Expand Down Expand Up @@ -283,7 +283,7 @@ The AI Assistant runs the tasks requested in the message and creates a conversat
It might take a minute or two for the AI Assistant to process the message and create the conversation.

Note that overly broad prompts may result in the request exceeding token limits.
For more information, refer to <DocLink slug="/serverless/observability/ai-assistant" section="token-limits" />
For more information, refer to <DocLink slug="/serverless/observability/ai-assistant" section="token-limits" />.
Also, attempting to analyze several alerts in a single connector execution may cause you to exceed the function call limit.
If this happens, modify the message specified in the connector configuration to avoid exceeding limits.

Expand Down
Loading