[Observability AI Assistant] rule connector - handle multiple prompt #209221
Merged
arturoliduena merged 5 commits intoelastic:mainfrom Feb 5, 2025
Conversation
arturoliduena
added
release_note:feature
Contributor
|
Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant) |
7 tasks
sorenlouv
reviewed
Feb 3, 2025
.../observability/plugins/observability_ai_assistant_app/public/rule_connector/ai_assistant.tsx
Outdated
Show resolved
Hide resolved
Contributor
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]Page load bundle
History
|
pmuellr
approved these changes
Feb 3, 2025
Contributor
pmuellr
left a comment
pmuellr
left a comment
There was a problem hiding this comment.
LGTM, if I understand what's going on. This is an intermediate change to be released before #203729, which changes the connector schema in such a way that it continues to accept the "old format" but won't be setting any of the "new format" fields yet. In the follow-on PR 203729, to be released after this PR has been merged to serverless, the "new format" will be available to all Kibana instances running in serverless, both "old" (running this PR) and "new" (running 203729).
…ant_app/public/rule_connector/ai_assistant.tsx Co-authored-by: Søren Louv-Jansen <sorenlouv@gmail.com>
arturoliduena
force-pushed
the
185032-o11y-AI-Assistant-action-intermediate-releases-trigger-on-alert-status-change
branch
from
6070011 to
002f1ba
Compare
sorenlouv
reviewed
Feb 4, 2025
| ) | ||
| ), | ||
| status: schema.maybe(schema.string()), | ||
| message: schema.maybe(schema.string({ minLength: 1 })), // this is a legacy field |
Contributor
There was a problem hiding this comment.
When can this be removed? Should we add a TODO: remove in 9.1 or something like that?
Contributor
Author
There was a problem hiding this comment.
As far as I understand, action parameters generated by an old action connector will retain the same schema, so we need to keep this property to ensure backward compatibility.
sorenlouv
reviewed
Feb 4, 2025
| logger: Logger | ||
| ): Promise<void> { | ||
| const alerts = { | ||
| new: [...(params.alerts?.new || [])], |
Contributor
There was a problem hiding this comment.
Do you need the spread?
Suggested change
| new: [...(params.alerts?.new || [])], | |
| new: params.alerts?.new || [], |
Contributor
Author
There was a problem hiding this comment.
Yes, I used spread operator to create a shallow copy of the params alerts.
sorenlouv
reviewed
Feb 4, 2025
| ): Promise<void> { | ||
| const alerts = { | ||
| new: [...(params.alerts?.new || [])], | ||
| recovered: [...(params.alerts?.recovered || [])], |
sorenlouv
approved these changes
Feb 4, 2025
Contributor
Author
Thanks, @pmuellr! Yes, that’s correct. This PR is an intermediate step to ensure compatibility before #203729 is released |
Contributor
|
Starting backport for target branches: 8.18 https://github.com/elastic/kibana/actions/runs/13154015918 |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
kibanamachine
added
the
backport missing
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
drewdaemon
pushed a commit
to drewdaemon/kibana
that referenced
this pull request
Feb 6, 2025
…lastic#209221) Intermediate releases to change rule or connector schemas in serverless for elastic#185032 ## Summary An Observability AI Assistant connector is available to be set as action for Observability rules. When an alert is triggered, a conversation with the AI assistant will be created sending the initial prompt set by the user in the rule action. The conversation is then stored and can be retrieved from the AI Assistant interface. the action is triggered on any status change of the alert (active, recovered, untracked), creating a new conversation for each of them using the same initial prompt which may not be suitable for the 3 cases. Improvement The user is able to choose in when the action should be run (active, recovered, untracked, all),. That would allow the user to specify more than one AI Assistant action, with a different and more suitable prompt in each case.
arturoliduena
added a commit
to arturoliduena/kibana
that referenced
this pull request
Feb 7, 2025
…lastic#209221) Intermediate releases to change rule or connector schemas in serverless for elastic#185032 ## Summary An Observability AI Assistant connector is available to be set as action for Observability rules. When an alert is triggered, a conversation with the AI assistant will be created sending the initial prompt set by the user in the rule action. The conversation is then stored and can be retrieved from the AI Assistant interface. the action is triggered on any status change of the alert (active, recovered, untracked), creating a new conversation for each of them using the same initial prompt which may not be suitable for the 3 cases. Improvement The user is able to choose in when the action should be run (active, recovered, untracked, all),. That would allow the user to specify more than one AI Assistant action, with a different and more suitable prompt in each case. (cherry picked from commit 3924e09) # Conflicts: # x-pack/solutions/observability/plugins/observability_ai_assistant_app/tsconfig.json
arturoliduena
added a commit
that referenced
this pull request
Feb 7, 2025
…prompt (#209221) (#210050) # Backport This will backport the following commits from `main` to `8.18`: - [[Observability AI Assistant] rule connector - handle multiple prompt (#209221)](#209221) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T09:16:42Z","message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport missing","release_note:feature","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0"],"title":"[Observability AI Assistant] rule connector - handle multiple prompt ","number":209221,"url":"https://github.com/elastic/kibana/pull/209221","mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209221","number":209221,"mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}}]}] BACKPORT-->
kibanamachine
removed
the
backport missing
arturoliduena
added
v8.19.0
v9.0.0
backport:version
Contributor
|
Starting backport for target branches: 8.18, 8.x, 9.0 https://github.com/elastic/kibana/actions/runs/13241091303 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 10, 2025
…lastic#209221) Intermediate releases to change rule or connector schemas in serverless for elastic#185032 ## Summary An Observability AI Assistant connector is available to be set as action for Observability rules. When an alert is triggered, a conversation with the AI assistant will be created sending the initial prompt set by the user in the rule action. The conversation is then stored and can be retrieved from the AI Assistant interface. the action is triggered on any status change of the alert (active, recovered, untracked), creating a new conversation for each of them using the same initial prompt which may not be suitable for the 3 cases. Improvement The user is able to choose in when the action should be run (active, recovered, untracked, all),. That would allow the user to specify more than one AI Assistant action, with a different and more suitable prompt in each case. (cherry picked from commit 3924e09)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Feb 10, 2025
…rompt (#209221) (#210357) # Backport This will backport the following commits from `main` to `9.0`: - [[Observability AI Assistant] rule connector - handle multiple prompt (#209221)](#209221) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T09:16:42Z","message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Observability AI Assistant] rule connector - handle multiple prompt ","number":209221,"url":"https://github.com/elastic/kibana/pull/209221","mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210050","number":210050,"state":"MERGED","mergeCommit":{"sha":"2d36c65bc3840ee83858ecca678ebd499a935602","message":"[8.18] [Observability AI Assistant] rule connector - handle multiple prompt (#209221) (#210050)\n\n# Backport\r\n\r\nThis will backport the following commits from `main` to `8.18`:\r\n- [[Observability AI Assistant] rule connector - handle multiple prompt\r\n(#209221)](https://github.com/elastic/kibana/pull/209221)\r\n\r\n<!--- Backport version: 9.6.4 -->\r\n\r\n### Questions ?\r\nPlease refer to the [Backport tool\r\ndocumentation](https://github.com/sorenlouv/backport)\r\n\r\n<!--BACKPORT [{\"author\":{\"name\":\"Arturo\r\nLidueña\",\"email\":\"arturo.liduena@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T09:16:42Z\",\"message\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\r\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\r\nAI Assistant connector is available to be set as action\\r\\nfor\r\nObservability rules. When an alert is triggered, a conversation\r\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\r\nby the\\r\\nuser in the rule action. The conversation is then stored and\r\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\r\ntriggered on\\r\\nany status change of the alert (active, recovered,\r\nuntracked), creating\\r\\na new conversation for each of them using the\r\nsame initial prompt which\\r\\nmay not be suitable for the 3\r\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\r\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\r\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\r\ndifferent and more suitable prompt\\r\\nin each\r\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"backport\r\nmissing\",\"release_note:feature\",\"Team:Obs AI\r\nAssistant\",\"backport:version\",\"v8.18.0\",\"v9.1.0\"],\"title\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n\",\"number\":209221,\"url\":\"https://github.com/elastic/kibana/pull/209221\",\"mergeCommit\":{\"message\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\r\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\r\nAI Assistant connector is available to be set as action\\r\\nfor\r\nObservability rules. When an alert is triggered, a conversation\r\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\r\nby the\\r\\nuser in the rule action. The conversation is then stored and\r\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\r\ntriggered on\\r\\nany status change of the alert (active, recovered,\r\nuntracked), creating\\r\\na new conversation for each of them using the\r\nsame initial prompt which\\r\\nmay not be suitable for the 3\r\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\r\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\r\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\r\ndifferent and more suitable prompt\\r\\nin each\r\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.18\"],\"targetPullRequestStates\":[{\"branch\":\"8.18\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209221\",\"number\":209221,\"mergeCommit\":{\"message\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\r\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\r\nAI Assistant connector is available to be set as action\\r\\nfor\r\nObservability rules. When an alert is triggered, a conversation\r\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\r\nby the\\r\\nuser in the rule action. The conversation is then stored and\r\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\r\ntriggered on\\r\\nany status change of the alert (active, recovered,\r\nuntracked), creating\\r\\na new conversation for each of them using the\r\nsame initial prompt which\\r\\nmay not be suitable for the 3\r\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\r\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\r\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\r\ndifferent and more suitable prompt\\r\\nin each\r\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\"}}]}] BACKPORT-->"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209221","number":209221,"mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co>
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
arturoliduena
added a commit
to arturoliduena/kibana
that referenced
this pull request
Feb 12, 2025
…lastic#209221) Intermediate releases to change rule or connector schemas in serverless for elastic#185032 ## Summary An Observability AI Assistant connector is available to be set as action for Observability rules. When an alert is triggered, a conversation with the AI assistant will be created sending the initial prompt set by the user in the rule action. The conversation is then stored and can be retrieved from the AI Assistant interface. the action is triggered on any status change of the alert (active, recovered, untracked), creating a new conversation for each of them using the same initial prompt which may not be suitable for the 3 cases. Improvement The user is able to choose in when the action should be run (active, recovered, untracked, all),. That would allow the user to specify more than one AI Assistant action, with a different and more suitable prompt in each case. (cherry picked from commit 3924e09) # Conflicts: # x-pack/solutions/observability/plugins/observability_ai_assistant_app/tsconfig.json
arturoliduena
added a commit
that referenced
this pull request
Feb 12, 2025
…rompt (#209221) (#210774) # Backport This will backport the following commits from `main` to `8.x`: - [[Observability AI Assistant] rule connector - handle multiple prompt (#209221)](#209221) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T09:16:42Z","message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Observability AI Assistant] rule connector - handle multiple prompt ","number":209221,"url":"https://github.com/elastic/kibana/pull/209221","mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210357","number":210357,"state":"MERGED","mergeCommit":{"sha":"5908ba19e7419dd1757fb401dcd85bce01ffd262","message":"[9.0] [Observability AI Assistant] rule connector - handle multiple prompt (#209221) (#210357)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Observability AI Assistant] rule connector - handle multiple prompt\n(#209221)](https://github.com/elastic/kibana/pull/209221)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Arturo\nLidueña\",\"email\":\"arturo.liduena@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T09:16:42Z\",\"message\":\"[Observability\nAI Assistant] rule connector - handle multiple prompt\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\nAI Assistant connector is available to be set as action\\r\\nfor\nObservability rules. When an alert is triggered, a conversation\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\nby the\\r\\nuser in the rule action. The conversation is then stored and\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\ntriggered on\\r\\nany status change of the alert (active, recovered,\nuntracked), creating\\r\\na new conversation for each of them using the\nsame initial prompt which\\r\\nmay not be suitable for the 3\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\ndifferent and more suitable prompt\\r\\nin each\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"v9.0.0\",\"release_note:feature\",\"Team:Obs\nAI\nAssistant\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[Observability\nAI Assistant] rule connector - handle multiple prompt\n\",\"number\":209221,\"url\":\"https://github.com/elastic/kibana/pull/209221\",\"mergeCommit\":{\"message\":\"[Observability\nAI Assistant] rule connector - handle multiple prompt\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\nAI Assistant connector is available to be set as action\\r\\nfor\nObservability rules. When an alert is triggered, a conversation\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\nby the\\r\\nuser in the rule action. The conversation is then stored and\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\ntriggered on\\r\\nany status change of the alert (active, recovered,\nuntracked), creating\\r\\na new conversation for each of them using the\nsame initial prompt which\\r\\nmay not be suitable for the 3\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\ndifferent and more suitable prompt\\r\\nin each\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.18\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/210050\",\"number\":210050,\"state\":\"MERGED\",\"mergeCommit\":{\"sha\":\"2d36c65bc3840ee83858ecca678ebd499a935602\",\"message\":\"[8.18]\n[Observability AI Assistant] rule connector - handle multiple prompt\n(#209221) (#210050)\\n\\n# Backport\\r\\n\\r\\nThis will backport the\nfollowing commits from `main` to `8.18`:\\r\\n- [[Observability AI\nAssistant] rule connector - handle multiple\nprompt\\r\\n(#209221)](https://github.com/elastic/kibana/pull/209221)\\r\\n\\r\\n<!---\nBackport version: 9.6.4 -->\\r\\n\\r\\n### Questions ?\\r\\nPlease refer to\nthe [Backport\ntool\\r\\ndocumentation](https://github.com/sorenlouv/backport)\\r\\n\\r\\n<!--BACKPORT\n[{\\\"author\\\":{\\\"name\\\":\\\"Arturo\\r\\nLidueña\\\",\\\"email\\\":\\\"arturo.liduena@elastic.co\\\"},\\\"sourceCommit\\\":{\\\"committedDate\\\":\\\"2025-02-05T09:16:42Z\\\",\\\"message\\\":\\\"[Observability\\r\\nAI\nAssistant] rule connector - handle multiple\nprompt\\r\\n(#209221)\\\\n\\\\nIntermediate releases to change rule or\nconnector schemas\\r\\nin serverless\\\\r\\\\nfor #185032\\\\r\\\\n\\\\r\\\\n##\nSummary\\\\r\\\\n\\\\r\\\\nAn Observability\\r\\nAI Assistant connector is\navailable to be set as action\\\\r\\\\nfor\\r\\nObservability rules. When an\nalert is triggered, a conversation\\r\\nwith\\\\r\\\\nthe AI assistant will be\ncreated sending the initial prompt set\\r\\nby the\\\\r\\\\nuser in the rule\naction. The conversation is then stored and\\r\\ncan be\\\\r\\\\nretrieved\nfrom the AI Assistant interface. the action is\\r\\ntriggered on\\\\r\\\\nany\nstatus change of the alert (active, recovered,\\r\\nuntracked),\ncreating\\\\r\\\\na new conversation for each of them using the\\r\\nsame\ninitial prompt which\\\\r\\\\nmay not be suitable for the\n3\\r\\ncases.\\\\r\\\\n\\\\r\\\\nImprovement\\\\r\\\\nThe user is able to choose in\nwhen the\\r\\naction should be run (active,\\\\r\\\\nrecovered, untracked,\nall),. That would\\r\\nallow the user to specify more\\\\r\\\\nthan one AI\nAssistant action, with a\\r\\ndifferent and more suitable prompt\\\\r\\\\nin\neach\\r\\ncase.\\\",\\\"sha\\\":\\\"3924e095c5d9791e7a83208fdde6e542de1475bb\\\",\\\"branchLabelMapping\\\":{\\\"^v9.1.0$\\\":\\\"main\\\",\\\"^v8.19.0$\\\":\\\"8.x\\\",\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\":\\\"$1.$2\\\"}},\\\"sourcePullRequest\\\":{\\\"labels\\\":[\\\"backport\\r\\nmissing\\\",\\\"release_note:feature\\\",\\\"Team:Obs\nAI\\r\\nAssistant\\\",\\\"backport:version\\\",\\\"v8.18.0\\\",\\\"v9.1.0\\\"],\\\"title\\\":\\\"[Observability\\r\\nAI\nAssistant] rule connector - handle multiple\nprompt\\r\\n\\\",\\\"number\\\":209221,\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/209221\\\",\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Observability\\r\\nAI\nAssistant] rule connector - handle multiple\nprompt\\r\\n(#209221)\\\\n\\\\nIntermediate releases to change rule or\nconnector schemas\\r\\nin serverless\\\\r\\\\nfor #185032\\\\r\\\\n\\\\r\\\\n##\nSummary\\\\r\\\\n\\\\r\\\\nAn Observability\\r\\nAI Assistant connector is\navailable to be set as action\\\\r\\\\nfor\\r\\nObservability rules. When an\nalert is triggered, a conversation\\r\\nwith\\\\r\\\\nthe AI assistant will be\ncreated sending the initial prompt set\\r\\nby the\\\\r\\\\nuser in the rule\naction. The conversation is then stored and\\r\\ncan be\\\\r\\\\nretrieved\nfrom the AI Assistant interface. the action is\\r\\ntriggered on\\\\r\\\\nany\nstatus change of the alert (active, recovered,\\r\\nuntracked),\ncreating\\\\r\\\\na new conversation for each of them using the\\r\\nsame\ninitial prompt which\\\\r\\\\nmay not be suitable for the\n3\\r\\ncases.\\\\r\\\\n\\\\r\\\\nImprovement\\\\r\\\\nThe user is able to choose in\nwhen the\\r\\naction should be run (active,\\\\r\\\\nrecovered, untracked,\nall),. That would\\r\\nallow the user to specify more\\\\r\\\\nthan one AI\nAssistant action, with a\\r\\ndifferent and more suitable prompt\\\\r\\\\nin\neach\\r\\ncase.\\\",\\\"sha\\\":\\\"3924e095c5d9791e7a83208fdde6e542de1475bb\\\"}},\\\"sourceBranch\\\":\\\"main\\\",\\\"suggestedTargetBranches\\\":[\\\"8.18\\\"],\\\"targetPullRequestStates\\\":[{\\\"branch\\\":\\\"8.18\\\",\\\"label\\\":\\\"v8.18.0\\\",\\\"branchLabelMappingKey\\\":\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"},{\\\"branch\\\":\\\"main\\\",\\\"label\\\":\\\"v9.1.0\\\",\\\"branchLabelMappingKey\\\":\\\"^v9.1.0$\\\",\\\"isSourceBranch\\\":true,\\\"state\\\":\\\"MERGED\\\",\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/209221\\\",\\\"number\\\":209221,\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Observability\\r\\nAI\nAssistant] rule connector - handle multiple\nprompt\\r\\n(#209221)\\\\n\\\\nIntermediate releases to change rule or\nconnector schemas\\r\\nin serverless\\\\r\\\\nfor #185032\\\\r\\\\n\\\\r\\\\n##\nSummary\\\\r\\\\n\\\\r\\\\nAn Observability\\r\\nAI Assistant connector is\navailable to be set as action\\\\r\\\\nfor\\r\\nObservability rules. When an\nalert is triggered, a conversation\\r\\nwith\\\\r\\\\nthe AI assistant will be\ncreated sending the initial prompt set\\r\\nby the\\\\r\\\\nuser in the rule\naction. The conversation is then stored and\\r\\ncan be\\\\r\\\\nretrieved\nfrom the AI Assistant interface. the action is\\r\\ntriggered on\\\\r\\\\nany\nstatus change of the alert (active, recovered,\\r\\nuntracked),\ncreating\\\\r\\\\na new conversation for each of them using the\\r\\nsame\ninitial prompt which\\\\r\\\\nmay not be suitable for the\n3\\r\\ncases.\\\\r\\\\n\\\\r\\\\nImprovement\\\\r\\\\nThe user is able to choose in\nwhen the\\r\\naction should be run (active,\\\\r\\\\nrecovered, untracked,\nall),. That would\\r\\nallow the user to specify more\\\\r\\\\nthan one AI\nAssistant action, with a\\r\\ndifferent and more suitable prompt\\\\r\\\\nin\neach\\r\\ncase.\\\",\\\"sha\\\":\\\"3924e095c5d9791e7a83208fdde6e542de1475bb\\\"}}]}]\nBACKPORT-->\"}},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209221\",\"number\":209221,\"mergeCommit\":{\"message\":\"[Observability\nAI Assistant] rule connector - handle multiple prompt\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\nAI Assistant connector is available to be set as action\\r\\nfor\nObservability rules. When an alert is triggered, a conversation\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\nby the\\r\\nuser in the rule action. The conversation is then stored and\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\ntriggered on\\r\\nany status change of the alert (active, recovered,\nuntracked), creating\\r\\na new conversation for each of them using the\nsame initial prompt which\\r\\nmay not be suitable for the 3\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\ndifferent and more suitable prompt\\r\\nin each\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Arturo Lidueña <arturo.liduena@elastic.co>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210050","number":210050,"state":"MERGED","mergeCommit":{"sha":"2d36c65bc3840ee83858ecca678ebd499a935602","message":"[8.18] [Observability AI Assistant] rule connector - handle multiple prompt (#209221) (#210050)\n\n# Backport\r\n\r\nThis will backport the following commits from `main` to `8.18`:\r\n- [[Observability AI Assistant] rule connector - handle multiple prompt\r\n(#209221)](https://github.com/elastic/kibana/pull/209221)\r\n\r\n<!--- Backport version: 9.6.4 -->\r\n\r\n### Questions ?\r\nPlease refer to the [Backport tool\r\ndocumentation](https://github.com/sorenlouv/backport)\r\n\r\n<!--BACKPORT [{\"author\":{\"name\":\"Arturo\r\nLidueña\",\"email\":\"arturo.liduena@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T09:16:42Z\",\"message\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\r\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\r\nAI Assistant connector is available to be set as action\\r\\nfor\r\nObservability rules. When an alert is triggered, a conversation\r\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\r\nby the\\r\\nuser in the rule action. The conversation is then stored and\r\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\r\ntriggered on\\r\\nany status change of the alert (active, recovered,\r\nuntracked), creating\\r\\na new conversation for each of them using the\r\nsame initial prompt which\\r\\nmay not be suitable for the 3\r\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\r\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\r\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\r\ndifferent and more suitable prompt\\r\\nin each\r\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"backport\r\nmissing\",\"release_note:feature\",\"Team:Obs AI\r\nAssistant\",\"backport:version\",\"v8.18.0\",\"v9.1.0\"],\"title\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n\",\"number\":209221,\"url\":\"https://github.com/elastic/kibana/pull/209221\",\"mergeCommit\":{\"message\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\r\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\r\nAI Assistant connector is available to be set as action\\r\\nfor\r\nObservability rules. When an alert is triggered, a conversation\r\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\r\nby the\\r\\nuser in the rule action. The conversation is then stored and\r\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\r\ntriggered on\\r\\nany status change of the alert (active, recovered,\r\nuntracked), creating\\r\\na new conversation for each of them using the\r\nsame initial prompt which\\r\\nmay not be suitable for the 3\r\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\r\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\r\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\r\ndifferent and more suitable prompt\\r\\nin each\r\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.18\"],\"targetPullRequestStates\":[{\"branch\":\"8.18\",\"label\":\"v8.18.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209221\",\"number\":209221,\"mergeCommit\":{\"message\":\"[Observability\r\nAI Assistant] rule connector - handle multiple prompt\r\n(#209221)\\n\\nIntermediate releases to change rule or connector schemas\r\nin serverless\\r\\nfor #185032\\r\\n\\r\\n## Summary\\r\\n\\r\\nAn Observability\r\nAI Assistant connector is available to be set as action\\r\\nfor\r\nObservability rules. When an alert is triggered, a conversation\r\nwith\\r\\nthe AI assistant will be created sending the initial prompt set\r\nby the\\r\\nuser in the rule action. The conversation is then stored and\r\ncan be\\r\\nretrieved from the AI Assistant interface. the action is\r\ntriggered on\\r\\nany status change of the alert (active, recovered,\r\nuntracked), creating\\r\\na new conversation for each of them using the\r\nsame initial prompt which\\r\\nmay not be suitable for the 3\r\ncases.\\r\\n\\r\\nImprovement\\r\\nThe user is able to choose in when the\r\naction should be run (active,\\r\\nrecovered, untracked, all),. That would\r\nallow the user to specify more\\r\\nthan one AI Assistant action, with a\r\ndifferent and more suitable prompt\\r\\nin each\r\ncase.\",\"sha\":\"3924e095c5d9791e7a83208fdde6e542de1475bb\"}}]}] BACKPORT-->"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209221","number":209221,"mergeCommit":{"message":"[Observability AI Assistant] rule connector - handle multiple prompt (#209221)\n\nIntermediate releases to change rule or connector schemas in serverless\r\nfor #185032\r\n\r\n## Summary\r\n\r\nAn Observability AI Assistant connector is available to be set as action\r\nfor Observability rules. When an alert is triggered, a conversation with\r\nthe AI assistant will be created sending the initial prompt set by the\r\nuser in the rule action. The conversation is then stored and can be\r\nretrieved from the AI Assistant interface. the action is triggered on\r\nany status change of the alert (active, recovered, untracked), creating\r\na new conversation for each of them using the same initial prompt which\r\nmay not be suitable for the 3 cases.\r\n\r\nImprovement\r\nThe user is able to choose in when the action should be run (active,\r\nrecovered, untracked, all),. That would allow the user to specify more\r\nthan one AI Assistant action, with a different and more suitable prompt\r\nin each case.","sha":"3924e095c5d9791e7a83208fdde6e542de1475bb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intermediate releases to change rule or connector schemas in serverless for #185032
Summary
An Observability AI Assistant connector is available to be set as action for Observability rules. When an alert is triggered, a conversation with the AI assistant will be created sending the initial prompt set by the user in the rule action. The conversation is then stored and can be retrieved from the AI Assistant interface. the action is triggered on any status change of the alert (active, recovered, untracked), creating a new conversation for each of them using the same initial prompt which may not be suitable for the 3 cases.
Improvement
The user is able to choose in when the action should be run (active, recovered, untracked, all),. That would allow the user to specify more than one AI Assistant action, with a different and more suitable prompt in each case.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.