Add streaming to AI Insights by yuliia-fryshko · Pull Request #247644 · elastic/kibana

yuliia-fryshko · 2025-12-30T17:23:08Z

Close #440

This PR adds streaming support to all AI insights (log, error, and alert insights) in the Observability Agent Builder.

Changes in the PR:

Updated insight generation functions to return Observables instead of Promises: getLogAiInsights(),generateErrorAiInsight(), getAlertAiInsight()
Added Stop generating button during streaming
Added "Regenerate" button after stopping

Examples:

Alert AI Insights:

Screen.Recording.2026-01-08.at.12.39.52.mov

Error Ai Insights:

Screen.Recording.2026-01-08.at.12.43.17.mov

Log Ai Insights:

Screen.Recording.2026-01-08.at.12.44.35.mov

viduni94 · 2025-12-30T17:54:02Z

-    DefaultClientOptions
-  >({ http });
+  const fetchInsight = async (signal?: AbortSignal) => {
+    const response = await http.fetch('/internal/observability_agent_builder/ai_insights/alert', {


Why was the use of the API client reverted. We want to keep using the typed API client from server-route-repository, ideally.

viduni94 · 2025-12-30T17:58:59Z

+            </EuiButtonEmpty>
+          </ButtonSection>
+        ) : wasStopped ? (
+          <ButtonSection>


The regenerate button next to the "Start Conversation" (similar to contextual insights) might look a bit better I feel.

Also can you add a "loading animation/cursor" similar to contextual insights

Screen.Recording.2025-12-30.at.12.55.57.PM.mov

viduni94 · 2025-12-30T18:03:15Z

-            </EuiFlexGroup>
-          </>
+        {isLoading ? (
+          <ButtonSection>


When the buttons are outside of the EuiPanel it looks a bit odd, can we move them inside the panel similar to contextual insights?

…-insight

neptunian · 2026-01-05T17:48:47Z

-  const fetchInsight = async () => {
-    const response = await apiClient.fetch(
+  const fetchInsight = async (signal?: AbortSignal) => {
+    const response = (await apiClient.fetch(


Can you make apiClient a hook while we're in here as we're repeating some code in the insight components. Something like:

export function useApiClient() { const { services: { http }, } = useKibana(); return createRepositoryClient< ObservabilityAgentBuilderServerRouteRepository, DefaultClientOptions >({ http }); }

Thank you, @neptunian ! It's a good suggestion, I created the hook use_api_client

viduni94

Thanks for the changes @yuliia-fryshko
Added some comments.

Can you also add tests for the observability_agent_builder/public/components/ai_insight/ai_insight.tsx component and use_streaming_ai_insight hook?

viduni94 · 2026-01-05T17:07:16Z

+import { AbortError } from '@kbn/kibana-utils-plugin/common';
+import { httpResponseIntoObservable } from '@kbn/sse-utils-client';
+
+interface InsightState {


Should this be

Suggested change

interface InsightState {

interface InsightResponse {

viduni94 · 2026-01-05T17:08:20Z

+          },
+          { summary: '', context: '' }
+        ),
+        takeUntil(abort$)


Instead of having setIsLoading(false); in line 36, you probably could do:

Suggested change

takeUntil(abort$)

takeUntil(abort$),

finalize(() => setIsLoading(false))

This guarantees that setIsLoading(false) runs regardless of how the stream ends (complete, error, or unsubscribe)

viduni94 · 2026-01-05T17:09:16Z

+        takeUntil(abort$)
+      );
+
+      const subscription = observable$.subscribe({


Suggested change

const subscription = observable$.subscribe({

subscriptionRef.current = observable$.subscribe({

viduni94 · 2026-01-05T17:09:22Z

+        },
+      });
+
+      subscriptionRef.current = subscription;


Suggested change

subscriptionRef.current = subscription;

viduni94 · 2026-01-05T17:47:55Z

+        asResponse: true,
+        rawResponse: true,
      }
-    );
-    return response;
+    )) as unknown as { response: Response };


Can we avoid manually adding asResponse and rawResponse to each endpoint and also can we avoid as unknown as?
Instead, you can use the inbuilt stream method from the API client:

const createStream = useCallback( (signal: AbortSignal) => apiClient.stream('POST /internal/observability_agent_builder/ai_insights/log', { signal, params: { body: { alertId, }, }, }), [apiClient, alertId] );

Note: This may require some changes in the use_streaming_ai_insight hook

Thank you, Viduni! For pointing to it, I wanted refactor it as well a bit .

Replaced manual asResponse/rawResponse flags and type casting with apiClient.stream(), updated useStreamingAiInsight to accept Observable<StreamEvent> instead of Promise<Response>

viduni94 · 2026-01-05T17:48:09Z

+        asResponse: true,
+        rawResponse: true,
      }
-    );
-    return {
-      summary: response.summary ?? '',
-      context: response.context ?? '',
-    };
+    )) as unknown as { response: Response };


See https://github.com/elastic/kibana/pull/247644/changes#r2662323708

viduni94 · 2026-01-05T17:48:15Z

+        asResponse: true,
+        rawResponse: true,
      }
-    );
-    return {
-      summary: response.summary,
-      context: response.context,
-    };
+    )) as unknown as { response: Response };


See https://github.com/elastic/kibana/pull/247644/changes#r2662323708

viduni94 · 2026-01-05T17:49:18Z

+              onClick={regenerate}
+            >
+              {i18n.translate('xpack.observabilityAgentBuilder.aiInsight.regenerateButton', {
+                defaultMessage: 'Regenerate',


Can you move the regenerate button to the right side?
Having it in the left side looks odd.

viduni94 · 2026-01-05T17:52:53Z

-              </EuiFlexItem>
-            </EuiFlexGroup>
-          </>
+        {isLoading ? (


Can you add a loading cursor animation when the response is loading? Something similar to what we had in contextual insights?

Also I feel like moving "Stop generating" and other buttons inside the EuiPanel similar to contextual insights looks better. WDYT?

Good suggestion. @viduni94 ! Changed it

viduni94 · 2026-01-19T16:35:59Z

+    try {
+      const observable$ = createStream(abortController.signal).pipe(
+        filter(
+          (event: InsightStreamEvent): event is InsightStreamEvent =>


This type guard seems redundant as the input is already typed as InsightStreamEvent

Thank you, Viduni! I removed alsp the condition checks for 'context' | 'chatCompletionChunk' | 'chatCompletionMessage', which are the only possible values of InsightStreamEvent.

viduni94 · 2026-01-19T16:40:19Z

+      const observable$ = createStream(abortController.signal).pipe(
+        filter(
+          (event: InsightStreamEvent): event is InsightStreamEvent =>
+            event.type === 'context' ||
+            event.type === 'chatCompletionChunk' ||
+            event.type === 'chatCompletionMessage'
+        ),
+        map((event: InsightStreamEvent): ParsedEvent => {
+          if (event.type === 'context') {
+            return { type: 'context', context: event.context };
+          }
+          if (event.type === 'chatCompletionChunk') {
+            return { type: 'chunk', content: event.content };
+          }
+          return { type: 'message', content: event.content };
+        }),
+        scan<ParsedEvent, InsightResponse>(
+          (acc, event) => {
+            if (event.type === 'context') {
+              return { ...acc, context: event.context || '' };
+            }
+            if (event.type === 'chunk') {
+              return { ...acc, summary: acc.summary + (event.content || '') };
+            }
+            if (event.type === 'message') {
+              return { ...acc, summary: event.content || '' };
+            }
+            return acc;
+          },
+          { summary: '', context: '' }
+        ),


Do we need these intermediate mapping steps?

Can this be simplified as:

Suggested change

const observable$ = createStream(abortController.signal).pipe(

filter(

(event: InsightStreamEvent): event is InsightStreamEvent =>

event.type === 'context' ||

event.type === 'chatCompletionChunk' ||

event.type === 'chatCompletionMessage'

),

map((event: InsightStreamEvent): ParsedEvent => {

if (event.type === 'context') {

return { type: 'context', context: event.context };

}

if (event.type === 'chatCompletionChunk') {

return { type: 'chunk', content: event.content };

}

return { type: 'message', content: event.content };

}),

scan<ParsedEvent, InsightResponse>(

(acc, event) => {

if (event.type === 'context') {

return { ...acc, context: event.context || '' };

}

if (event.type === 'chunk') {

return { ...acc, summary: acc.summary + (event.content || '') };

}

if (event.type === 'message') {

return { ...acc, summary: event.content || '' };

}

return acc;

},

{ summary: '', context: '' }

),

const observable$ = createStream(abortController.signal).pipe(

scan<InsightStreamEvent, InsightResponse>(

(acc, event) => {

if (event.type === 'context') {

return { ...acc, context: event.context };

}

if (event.type === 'chatCompletionChunk') {

return { ...acc, summary: acc.summary + event.content };

}

if (event.type === 'chatCompletionMessage') {

return { ...acc, summary: event.content };

}

return acc;

},

{ summary: '', context: '' }

),

Btw, I didn't test the above suggestion. Feel free to make any adjustments after testing.

viduni94 · 2026-01-19T17:06:48Z

+      expect(result.current.error).toBe('Boom');
+    });
+    unmount();
+  });


Can you add a test that tests calling stop() aborts the stream?

Good suggestion , I checked the hook and also added a test that verifies the regenerate button appears after stopping the stream

viduni94 · 2026-01-19T17:07:12Z

+interface ParsedEvent {
+  type: 'context' | 'chunk' | 'message';
+  context?: string;
+  content?: string;
+}


See comment - https://github.com/elastic/kibana/pull/247644/changes#r2705477560

Suggested change

interface ParsedEvent {

type: 'context' | 'chunk' | 'message';

context?: string;

content?: string;

}

viduni94 · 2026-01-19T17:09:49Z

+      abortController.signal.addEventListener('abort', () => {
+        subscriber.next();
+        subscriber.complete();
+      });


This event listener is added and not removed and can cause a memory leak.

Suggested change

abortController.signal.addEventListener('abort', () => {

subscriber.next();

subscriber.complete();

});

const handler = () => {

subscriber.next();

subscriber.complete();

};

abortController.signal.addEventListener('abort', handler);

return () => abortController.signal.removeEventListener('abort', handler);

viduni94 · 2026-01-19T17:22:12Z

+      if (typeof index !== 'string' || typeof id !== 'string') {
+        throw new Error('Index and id must be strings');
+      }


Why do we need to throw an error here?
There is a check for this already in line 63 and there is no way createStream can be called if the conditions of this check are satisfied yeah?

Instead you can do a type assertion for the params in line 54 and 55

index: index as string, id: id as string,

viduni94 · 2026-01-19T17:24:08Z

+    unmount();
+  });
+
+  it('shows error banner and retries on click', () => {


Suggested change

it('shows error banner and retries on click', () => {

it('displays an error banner with a retry button when an error occurs that refetches insights when clicked', () => {

OR you could consider splitting this into 2 tests and wrap in a describe block.

Example:

describe('when an error occurs', () => { it('displays an error banner', () => { ... }); it('refetches insights when retry button is clicked', () => { ... }); });

viduni94 · 2026-01-19T17:29:59Z

+    unmount();
+  });
+
+  it('renders regenerate and start conversation actions when summary exists', () => {


This test is testing too many things in a single test. Consider splitting is as follows:

Example:

describe('when a summary has been generated', () => { it('displays regenerate and start conversation buttons', () => { // Just check buttons exist }); it('calls regenerate when regenerate button is clicked', () => { // Test regenerate click }); it('opens the conversation flyout with correct attachments when start conversation is clicked', () => { // Test start conversation click }); });

viduni94 · 2026-01-19T17:32:40Z

+                  <EuiButtonEmpty
+                    data-test-subj="observabilityAgentBuilderRegenerateButton"
+                    size="s"
+                    iconType="sparkles"
+                    onClick={regenerate}
+                  >


We decided not to show the Regenerate button if there is no error yeah?
(Because we can't edit the prompt, there is no point in regenerating as the response will most likely be the same. Ideally it should only be shown if the stream was stopped mid response - and not show when the stream completes)

Did that decision change? (Maybe I missed something)

I’m fine with removing it. my understanding was that we wouldn’t want to add it as a separate ticket, because it would make sense to handle it within the prompt edit. But since we’re implementing the stop functionality, it wouldn’t hurt to keep it there anyway - we know that the LLM can give slightly different answers each time we call it.

Sorry if this was my misunderstanding. I will remove it, and thank you for pointing it out.

we know that the LLM can give slightly different answers each time we call it

I don't think a slight difference adds any value without being able to edit the prompt. If we decide to add the prompt editing functionality, we can introduce the Regenerate button at that point. For now, I think it's sufficient to show only when the stream is stopped mid-generation.

Yes, I removed the Regenerate btn in case we have received a full response

viduni94 · 2026-01-21T22:19:03Z

Merging main to pull in this fix - #249799

viduni94 · 2026-01-21T21:59:23Z

+      expect(buildAttachments).toHaveBeenCalledWith('Hello world', 'context');
+      expect(mockOpenConversationFlyout).toHaveBeenCalledWith({
+        newConversation: true,
+        attachments: [{ type: 'test', data: {} }],


Can you check for the agentId for OBSERVABILITY_AGENT_ID in here too?

viduni94 · 2026-01-21T22:10:12Z

+        height: 16px;
+        margin-left: 2px;
+        vertical-align: middle;
+        background-color: ${euiTheme.colors.darkShade};


This looks a little too dark. Is there a slightly lighter version?

viduni94 · 2026-01-21T22:16:05Z

+  });
+
+  describe('when an error occurs', () => {
+    it('displays an error banner', () => {


The test says "displays an error banner" but doesn't actually verify the error banner and message. We should verify that as well.

viduni94 · 2026-01-21T22:25:17Z

+              <EuiSpacer size="s" />
+              <EuiFlexGroup justifyContent="flexEnd" gutterSize="s" responsive={false}>
+                <EuiFlexItem grow={false}>
+                  <StartConversationButton onClick={handleStartConversation} />


I can start a conversation when the summary is emtpy

Click on the insight

Immediately click on Stop Generation --> The content is empty

"Start conversation" button is shown --> Click that and continue the conversation

Notice how an empty string is passed as the summary

Screen.Recording.2026-01-21.at.5.22.07.PM.mov

We shouldn't allow starting a conversation when the summary is empty.

Good catch, @viduni94 ! So, when the user clicked "stop conversation" we should show only "Regenerate " btn (without "Start conversation"), right?

We should definitely not show "Start conversation" when the summary is empty.

When there's a partial result:

Old contextual results show the "Start conversation" button

However, I'm not sure whether there's any value in starting a conversation with a partial summary - maybe there is.

Maybe worth checking with @isaclfreire

Hmm, I definitely think that if the summary is empty, it doesn’t make sense to start the conversation. But when the summary is partial, I think it depends on which parts are available. I don’t have a strong opinion on this.

I’d propose removing the “Start conversation” button when the summary is empty, and keeping it when the summary is partial. That said, I’m flexible and happy to change this now or later.

@viduni94

Screen.Recording.2026-01-22.at.20.02.37.mov

Sounds good! Let's leave it this way and update later if it comes up.

viduni94 · 2026-01-21T22:39:53Z

+          logger,
+          signal: getRequestAbortedSignal(request),
+        }),
+      }) as IKibanaResponse;


as IKibanaResponse is only included in 2 out of the 3 routes.
Can we remove it in all?

viduni94 · 2026-01-21T22:40:08Z

+          logger,
+          signal: getRequestAbortedSignal(request),
+        }),
+      }) as IKibanaResponse;


as IKibanaResponse is only included in 2 out of the 3 routes.
Can we remove it in all?

viduni94 · 2026-01-21T22:41:19Z

Thanks for the changes @yuliia-fryshko
The PR mostly looks good! The only blocker is this one - #247644 (comment)

viduni94

LGTM
Left a few comments about readability, cursor in dark mode and API client memoizing.

Thanks for all the changes @yuliia-fryshko

viduni94 · 2026-01-22T19:37:49Z

+          {isLoading ? (
+            <>
+              <EuiSpacer size="m" />
+              <EuiHorizontalRule margin="none" />
+              <EuiSpacer size="s" />
+              <EuiFlexGroup justifyContent="flexStart" gutterSize="s" responsive={false}>
+                <EuiFlexItem grow={false}>
+                  <EuiButtonEmpty
+                    data-test-subj="observabilityAgentBuilderStopGeneratingButton"
+                    color="text"
+                    iconType="stop"
+                    size="s"
+                    onClick={stop}
+                  >
+                    {i18n.translate(
+                      'xpack.observabilityAgentBuilder.aiInsight.stopGeneratingButton',
+                      {
+                        defaultMessage: 'Stop generating',
+                      }
+                    )}
+                  </EuiButtonEmpty>
+                </EuiFlexItem>
+              </EuiFlexGroup>
+            </>
+          ) : wasStopped ? (
+            <>
+              <EuiSpacer size="m" />
+              <EuiHorizontalRule margin="none" />
+              <EuiSpacer size="s" />
+              <EuiFlexGroup justifyContent="flexEnd" gutterSize="s" responsive={false}>
+                <EuiFlexItem grow={false}>
+                  <EuiButtonEmpty
+                    data-test-subj="observabilityAgentBuilderRegenerateButton"
+                    size="s"
+                    iconType="sparkles"
+                    onClick={regenerate}
+                  >
+                    {i18n.translate('xpack.observabilityAgentBuilder.aiInsight.regenerateButton', {
+                      defaultMessage: 'Regenerate',
+                    })}
+                  </EuiButtonEmpty>
+                </EuiFlexItem>
+                {Boolean(summary && summary.trim()) && (
+                  <EuiFlexItem grow={false}>
+                    <StartConversationButton onClick={handleStartConversation} />
+                  </EuiFlexItem>
+                )}
+              </EuiFlexGroup>
+            </>
+          ) : Boolean(summary && summary.trim()) ? (
+            <>
+              <EuiSpacer size="m" />
+              <EuiHorizontalRule margin="none" />
+              <EuiSpacer size="s" />
+              <EuiFlexGroup justifyContent="flexEnd" gutterSize="s" responsive={false}>
+                <EuiFlexItem grow={false}>


All the conditions here makes it very hard to read this component.
Can we improve it with something like:

const hasSummary = Boolean(summary?.trim()); const renderFooter = () => { if (isLoading) { return ( <EuiFlexGroup justifyContent="flexStart" gutterSize="s" responsive={false}> <EuiFlexItem grow={false}> <EuiButtonEmpty data-test-subj="observabilityAgentBuilderStopGeneratingButton" color="text" iconType="stop" size="s" onClick={stop} > {i18n.translate('xpack.observabilityAgentBuilder.aiInsight.stopGeneratingButton', { defaultMessage: 'Stop generating', })} </EuiButtonEmpty> </EuiFlexItem> </EuiFlexGroup> ); } if (wasStopped) { return ( <EuiFlexGroup justifyContent="flexEnd" gutterSize="s" responsive={false}> <EuiFlexItem grow={false}> <EuiButtonEmpty data-test-subj="observabilityAgentBuilderRegenerateButton" size="s" iconType="sparkles" onClick={regenerate} > {i18n.translate('xpack.observabilityAgentBuilder.aiInsight.regenerateButton', { defaultMessage: 'Regenerate', })} </EuiButtonEmpty> </EuiFlexItem> {hasSummary && ( <EuiFlexItem grow={false}> <StartConversationButton onClick={handleStartConversation} /> </EuiFlexItem> )} </EuiFlexGroup> ); } if (hasSummary) { return ( <EuiFlexGroup justifyContent="flexEnd" gutterSize="s" responsive={false}> <EuiFlexItem grow={false}> <StartConversationButton onClick={handleStartConversation} /> </EuiFlexItem> </EuiFlexGroup> ); } return null; }; // already exists if ( !hasConnectors || !agentBuilder || !isAgentChatExperienceEnabled || !hasAgentBuilderAccess || !hasEnterpriseLicense ) { return null; } const footer = renderFooter();

Then in the JSX:

<EuiPanel color="subdued"> {error ? ( <AiInsightErrorBanner error={error} onRetry={fetch} /> ) : ( <EuiText size="s"> <EuiMarkdownFormat textSize="s">{summary}</EuiMarkdownFormat> {isLoading && <LoadingCursor />} </EuiText> )} {footer && ( <> <EuiSpacer size="m" /> <EuiHorizontalRule margin="none" /> <EuiSpacer size="s" /> {footer} </> )} </EuiPanel>

WDYT?

viduni94 · 2026-01-22T19:49:41Z

+        height: 16px;
+        margin-left: 2px;
+        vertical-align: middle;
+        background: rgba(0, 0, 0, 0.25);


This won't work in dark mode

Maybe let's stick with euiTheme.colors.textSubdued

viduni94 · 2026-01-22T20:00:50Z

-    ObservabilityAgentBuilderServerRouteRepository,
-    DefaultClientOptions
-  >({ http });
+  const apiClient = useApiClient();


This re-creates the API client object on every render. Consider memoizing it in use_api_client.

import { useMemo } from 'react'; export function useApiClient(): RouteRepositoryClient<...> { const { services: { http }, } = useKibana(); return useMemo( () => createRepositoryClient< ObservabilityAgentBuilderServerRouteRepository, DefaultClientOptions >({ http }), [http] ); }

elasticmachine · 2026-01-23T13:09:23Z

💚 Build Succeeded

Buildkite Build
Commit: 563b593

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`observabilityAgentBuilder`	58	61	+3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`observabilityAgentBuilder`	15.8KB	18.2KB	+2.4KB

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
`observabilityAgentBuilder`	2	1	-1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`observabilityAgentBuilder`	6.4KB	6.6KB	+139.0B

History

cc @yuliia-fryshko

yuliia-fryshko added 4 commits December 30, 2025 17:27

added streamimg to observability ai insights

5b709bc

added streamimg to error ai insights

f5b7701

added streamimg to alert ai insights

adfa0d8

removed unused type and code

2b61974

yuliia-fryshko requested a review from a team as a code owner December 30, 2025 17:23

yuliia-fryshko self-assigned this Dec 30, 2025

yuliia-fryshko added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting labels Dec 30, 2025

viduni94 reviewed Dec 30, 2025

View reviewed changes

Merge remote-tracking branch 'upstream/main' into add-streamimg-to-ai…

be99599

…-insight

yuliia-fryshko force-pushed the add-streamimg-to-ai-insight branch from fcb4247 to be99599 Compare January 2, 2026 09:05

kibanamachine and others added 9 commits January 2, 2026 09:15

Changes from node scripts/lint_ts_projects --fix

d9dda81

Changes from node scripts/regenerate_moon_projects.js --update

d3826a5

Changes from node scripts/eslint_all_files --no-cache --fix

d86255f

Merge branch 'main' into add-streamimg-to-ai-insight

0fba3a9

use apiclient, rxjs instead of manually handling abort operations

a3ae8ff

Changes from node scripts/lint_ts_projects --fix

762e2c7

Changes from node scripts/regenerate_moon_projects.js --update

43a3347

added hook for handling streaming operations

a65342d

Changes from node scripts/eslint_all_files --no-cache --fix

d073803

neptunian reviewed Jan 5, 2026

View reviewed changes

viduni94 reviewed Jan 5, 2026

View reviewed changes

yuliia-fryshko added 8 commits January 8, 2026 10:08

Merge branch 'main' into add-streamimg-to-ai-insight

b9100db

added cursor loader

14613f2

added regenerate next to start conversation

42d1a76

added a hook use_api_client

fd3fa36

fixed merge conflicts

06f3188

renamed to InsightResponse and InsightStreamEvent

eb0cdf1

refactor streamimg hook

3693afb

exported getRequestAbortedSignal from Inference Plugin

5164de5

kibanamachine and others added 8 commits January 8, 2026 16:12

Changes from node scripts/regenerate_moon_projects.js --update

1e8bdcf

Changes from node scripts/eslint_all_files --no-cache --fix

d1247cf

Merge branch 'main' into add-streamimg-to-ai-insight

13a658a

Merge branch 'main' into add-streamimg-to-ai-insight

48e647c

Merge branch 'main' into add-streamimg-to-ai-insight

fad07af

Merge branch 'main' into add-streamimg-to-ai-insight

56559bd

added tests

ba6ed9f

Changes from node scripts/eslint_all_files --no-cache --fix

314e190

viduni94 reviewed Jan 19, 2026

View reviewed changes

yuliia-fryshko added 5 commits January 20, 2026 11:27

fixed review comments

08625df

removed markdown AST manipulation

8f62336

addressed review comments

8e2f16a

fixed merge conflicts

5b2a8eb

Merge branch 'main' into add-streamimg-to-ai-insight

e14f2d6

Merge branch 'main' into add-streamimg-to-ai-insight

005bf85

viduni94 reviewed Jan 21, 2026

View reviewed changes

yuliia-fryshko added 2 commits January 22, 2026 13:50

Merge branch 'main' into add-streamimg-to-ai-insight

ea2958c

Start Conversation btn is not available is summary is empty

b579083

viduni94 added the v9.4.0 label Jan 22, 2026

viduni94 approved these changes Jan 22, 2026

View reviewed changes

yuliia-fryshko added 3 commits January 23, 2026 10:02

fixed tests

43e59c9

Merge branch 'main' into add-streamimg-to-ai-insight

13faa71

Merge branch 'main' into add-streamimg-to-ai-insight

563b593

yuliia-fryshko added 2 commits January 23, 2026 16:43

Merge branch 'main' into add-streamimg-to-ai-insight

acd099c

Merge branch 'main' into add-streamimg-to-ai-insight

ff45961

yuliia-fryshko enabled auto-merge (squash) January 23, 2026 16:06

yuliia-fryshko merged commit 577ad1e into elastic:main Jan 23, 2026
15 of 16 checks passed

	takeUntil(abort$)
	takeUntil(abort$),
	finalize(() => setIsLoading(false))

	const subscription = observable$.subscribe({
	subscriptionRef.current = observable$.subscribe({

	it('shows error banner and retries on click', () => {
	it('displays an error banner with a retry button when an error occurs that refetches insights when clicked', () => {

Conversation

yuliia-fryshko commented Dec 30, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

viduni94 left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

viduni94 Jan 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

yuliia-fryshko commented Dec 30, 2025 •

edited

Loading

viduni94 Jan 5, 2026 •

edited

Loading

viduni94 Jan 21, 2026 •

edited

Loading

yuliia-fryshko Jan 21, 2026 •

edited

Loading