-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Obs AI Assistant] ai assistant system connector #179980
[Obs AI Assistant] ai assistant system connector #179980
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
/ci |
/ci |
/ci |
/ci |
/ci |
...gins/observability_solution/observability_ai_assistant/server/functions/execute_connector.ts
Outdated
Show resolved
Hide resolved
++ to what @dgieselaar said 🙂. |
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Obs-ux-management changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! There are some open comments but those can be addressed in a follow-up. Thanks for doing this, really exciting feature!
const extractAlertData = (hit: AlertHit) => { | ||
return { | ||
id: hit._id, | ||
reason: get(hit, 'kibana.alert.reason') || null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason why we would not send over the full alert data here? Maybe good to talk to @sorenlouv about this as well - we can also do it in a followup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to limit the noise and amount of token sent but that's probably too early for that. Updated in cfe8800
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
async chunk count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @klacabane |
…app (#180949) ## Summary Resolves #180910 This change simply moves the rule_connector introduced in #179980 to the `observability_ai_assistant_app` plugin. There are not functional changes. Also added some unit tests ### Testing See testing section in #179980 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
…app (elastic#180949) ## Summary Resolves elastic#180910 This change simply moves the rule_connector introduced in elastic#179980 to the `observability_ai_assistant_app` plugin. There are not functional changes. Also added some unit tests ### Testing See testing section in elastic#179980 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit e8fe9db)
Summary
Creates a system connector that can call the observability ai assistant to execute actions on behalf of user. The connector is tagged as tech preview.
The connector can be triggered when an alert fires. Connector can be configured with an initial message to the assistant which generates an answer and triggers potential actions on the assistant side. The current experimental scenario is to ask the assistant to generate a report of the alert that fired (by initially providing some context in the first message), recalling any information/potential resolutions of previous occurrences stored in the knowledge base and also including other active alerts that may be related. One last step that can be asked to the assistant is to trigger an action, currently only sending the report (or any other message) to a preconfigured slack webhook is supported.
Testing
Note: when asked to send a message to another connector (in our case slack), we'll try to include a link to the generated conversation. It is only possible to generate this link if server.publicBaseUrl is correctly set in kibana settings.
incoming-webhook
permissionError Count Threshold
and generate errors vianode scripts/synthtrace many_errors.ts --live
)TODO