[LLM tasks] Add product documentation retrieval task #194379

pgayvallet · 2024-09-30T07:47:51Z

Summary

Close #193473
Close #193474

This PR utilize the documentation packages that are build via the tool introduced by #193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call.

Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, retrieve_documentation (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up).

For more information, please refer to the self-review.

General architecture

What this PR does

Adds two plugin:

productDocBase: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part.
llmTasks: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the nlToEsql task will probably be moved to that plugin).
Add a retrieve_documentation tool registration for the o11y assistant
Add a component on the o11y assistant configuration page to install the product doc

(wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up)

What is NOT included in this PR:

Wire product base feature to the security assistant (should be done by the owning team as a follow-up)
- installation
- utilization as tool
FTR tests: this is somewhat blocked by the same things we need to figure out for https://github.com/elastic/kibana-team/issues/1271

Screenshots

Installation from o11y assistant configuration page

Example of output

Without product documentation installed

With product documentation installed

elasticmachine · 2024-09-30T11:18:15Z

Pinging @elastic/appex-ai-infra (Team:AI Infra)

afharo

kibana.jsonc LGTM

jbudz

packages/kbn-optimizer/limits.yml

…te --fix'

… src/core/server/integration_tests/ci_checks'

…egistry-plugin

pgayvallet · 2024-10-03T13:26:23Z

Moving back to draft as I will use the PR for the installation logic

…egistry-plugin

legrego

LGTM, thanks for addressing my previous feedback. Switching to use the task manager makes a lot of sense for our use case.

I have some non-blocking comments that we should address, either here or in a follow up.

Additionally, I'd like to test the install procedure in a memory constrained environment, such as a 1GB ESS instance.

docs/user/security/audit-logging.asciidoc

x-pack/plugins/ai_infra/product_doc_base/server/services/doc_manager/doc_manager.ts

x-pack/plugins/ai_infra/product_doc_base/server/tasks/utils.ts

legrego · 2024-11-14T16:20:48Z

x-pack/plugins/ai_infra/product_doc_base/server/tasks/install_all.ts

+    [INSTALL_ALL_TASK_TYPE]: {
+      title: 'Install all product documentation artifacts',
+      timeout: '10m',
+      maxAttempts: 3,


We should check with response ops about the cost attribute for all of our tasks (https://github.com/pgayvallet/kibana/blob/1ddad2f6cd6b23333a6d2070e50d705ec79ab2fd/x-pack/plugins/task_manager/server/task.ts#L21-L25).

We know this is a long-running task which is capable of emitting event loop utilization warnings. Right now our cost options are tiny, normal, and extra large. I'm not sure if this qualifies as extra large or not, but maybe response ops can help us determine the appropriate cost to select.

Good point. I asked Mike about this

Extra large means it needs a lot of CPU and memory resources compared to other typical background tasks (5x more than normal tasks). For example, indicator match rules in security solution.

Setting extra large indicates to task manager that it should consider these types of tasks as the equivalent of five normal background tasks, so it reduces overall task concurrency on the running node to accommodate these tasks. In general we recommend optimizing the task type for memory and CPU instead of setting extra large as it does affect Kibana throughput on a given node quite a bit when they run.

legrego · 2024-11-14T16:49:57Z

x-pack/plugins/ai_infra/product_doc_base/server/tasks/utils.ts

+  taskId: string;
+  timeout?: number;
+  interval?: number;
+}): Promise<boolean> => {


nit: the return value doesn't appear to be used anywhere

legrego · 2024-11-14T16:51:54Z

x-pack/plugins/ai_infra/product_doc_base/server/routes/installation.ts

+        wait: true,
+      });
+
+      return res.ok<PerformInstallResponse>({


This will incorrectly report installed: true if the task fails.
Steps:

Change the artifactRepositoryUrl to something that will not resolve

Navigate to o11y ai assistant settings

Click the Install button to invoke this endpoint

Wait for the request to complete. It will eventually return a successful response after TM exhausts all retry attempts.

Yeah.. working with remote task execution is quite awkward. The issue I have is that once executed, the task instance is deleted, so we can't even retrieve the output status from it. But maybe in case of error the instance is preserved... idk

So, I fixed it in b9145ef.

What I learned though, is that in case of task failure, the failure isn't stored anywhere (the task instance object still gets deleted at the end of the run), so

I have to manually detect if the task was successful or not (by checking install status after the run)...

meaning I can't surface the failure cause to the UI...

@pgayvallet nice, I think that'll work well enough given our constraints. Thanks for digging into this.

pgayvallet · 2024-11-15T13:00:22Z

Additionally, I'd like to test the install procedure in a memory constrained environment, such as a 1GB ESS instance.

@legrego on serverless oblt project (with, AFAIK, 1gb BG nodes):

Takes ~6mins, but install is successful

…egistry-plugin

pgayvallet · 2024-11-19T12:39:24Z

@elasticmachine merge upstream

elasticmachine · 2024-11-19T13:19:46Z

💚 Build Succeeded

Buildkite Build
Commit: 09f8b2d
Cloud Deployment
Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-194379-09f8b2db5249

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`observabilityAiAssistantManagement`	357	361	+4
`productDocBase`	-	7	+7
total			+11

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`@kbn/product-doc-common`	-	31	+31
`llmTasks`	-	1	+1
`productDocBase`	-	10	+10
total			+42

Async chunks

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

id	before	after	diff
`observabilityAiAssistantManagement`	93.1KB	97.7KB	+4.6KB

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
`llmTasks`	-	2	+2
`productDocBase`	-	4	+4
total			+6

Page load bundle

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

id	before	after	diff
`productDocBase`	-	2.2KB	+2.2KB

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/saved-objects-service.html#_mappings

id	before	after	diff
`product-doc-install-status`	-	6	+6

Unknown metric groups

API count

id	before	after	diff
`@kbn/product-doc-common`	-	31	+31
`llmTasks`	-	5	+5
`productDocBase`	-	10	+10
total			+46

ESLint disabled in files

id	before	after	diff
`llmTasks`	-	1	+1
`productDocBase`	-	2	+2
total			+3

Total ESLint disabled count

id	before	after	diff
`llmTasks`	-	1	+1
`productDocBase`	-	2	+2
total			+3

History

💛 Build #251767 was flaky 040956d
💚 Build #251757 succeeded a34e114
💔 Build #251661 failed 7063ce4
💔 Build #251314 failed 1ddad2f

kibanamachine · 2024-11-19T14:28:44Z

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/11915163871

kibanamachine · 2024-11-19T14:33:30Z

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts You might need to backport the following PRs to 8.x: - [Fleet] Filter integrations/packages list shown depending on the `policy_templates_behavior` field (#200605) - [Indx Mgmt] Enable semantic text adaptive allocations by default (#200168) - Swaps template literals for sprintf style interpolation (#200634) - Enabling Full FTR, Integration, and Unit tests to the FIPS Test Pipeline (#192632) - [Entity Analytics] [Entity Store] Refactor entity store enablement (server side) (#199638) - Authorized route migration for routes owned by security-detection-rule-management (#198383) - [ResponseOps][Connectors]Possible to open close incident in ServiceNow (#199989) - [ResponseOps][Connectors] Optional field blocks editing of case Webhook connector (#198314) - [Discover][Field caps] Align with the ES responses for closed indices (#199717) - Surface Kibana security route deprecations in Upgrade Assistant (#199656)

Manual backport

To create the backport manually run:

node scripts/backport --pr 194379

Questions ?

Please refer to the Backport tool documentation

pgayvallet · 2024-11-19T14:51:13Z

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

## Summary Close elastic#193473 Close elastic#193474 This PR utilize the documentation packages that are build via the tool introduced by elastic#193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call. Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, `retrieve_documentation` (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up). For more information, please refer to the self-review. ## General architecture <img width="1118" alt="Screenshot 2024-10-17 at 09 22 32" src="https://github.com/user-attachments/assets/3df8c30a-9ccc-49ab-92ce-c204b96d6fc4"> ## What this PR does Adds two plugin: - `productDocBase`: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part. - `llmTasks`: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the `nlToEsql` task will probably be moved to that plugin). - Add a `retrieve_documentation` tool registration for the o11y assistant - Add a component on the o11y assistant configuration page to install the product doc (wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up) ## What is NOT included in this PR: - Wire product base feature to the security assistant (should be done by the owning team as a follow-up) - installation - utilization as tool - FTR tests: this is somewhat blocked by the same things we need to figure out for elastic/kibana-team#1271 ## Screenshots ### Installation from o11y assistant configuration page <img width="1476" alt="Screenshot 2024-10-17 at 09 41 24" src="https://github.com/user-attachments/assets/31daa585-9fb2-400a-a2d1-5917a262367a"> ### Example of output #### Without product documentation installed <img width="739" alt="Screenshot 2024-10-10 at 09 59 41" src="https://github.com/user-attachments/assets/993fb216-6c9a-433f-bf44-f6e383d20d9d"> #### With product documentation installed <img width="718" alt="Screenshot 2024-10-10 at 09 55 38" src="https://github.com/user-attachments/assets/805ea4ca-8bc9-4355-a434-0ba81f8228a9"> --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Alex Szabo <[email protected]> Co-authored-by: Matthias Wilhelm <[email protected]> Co-authored-by: Elastic Machine <[email protected]> (cherry picked from commit 455c781) # Conflicts: # .github/CODEOWNERS

…200754) # Backport This will backport the following commits from `main` to `8.x`: - [[LLM tasks] Add product documentation retrieval task (#194379)](#194379)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport)

## Summary Close elastic#193473 Close elastic#193474 This PR utilize the documentation packages that are build via the tool introduced by elastic#193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call. Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, `retrieve_documentation` (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up). For more information, please refer to the self-review. ## General architecture <img width="1118" alt="Screenshot 2024-10-17 at 09 22 32" src="https://github.com/user-attachments/assets/3df8c30a-9ccc-49ab-92ce-c204b96d6fc4"> ## What this PR does Adds two plugin: - `productDocBase`: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part. - `llmTasks`: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the `nlToEsql` task will probably be moved to that plugin). - Add a `retrieve_documentation` tool registration for the o11y assistant - Add a component on the o11y assistant configuration page to install the product doc (wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up) ## What is NOT included in this PR: - Wire product base feature to the security assistant (should be done by the owning team as a follow-up) - installation - utilization as tool - FTR tests: this is somewhat blocked by the same things we need to figure out for elastic/kibana-team#1271 ## Screenshots ### Installation from o11y assistant configuration page <img width="1476" alt="Screenshot 2024-10-17 at 09 41 24" src="https://github.com/user-attachments/assets/31daa585-9fb2-400a-a2d1-5917a262367a"> ### Example of output #### Without product documentation installed <img width="739" alt="Screenshot 2024-10-10 at 09 59 41" src="https://github.com/user-attachments/assets/993fb216-6c9a-433f-bf44-f6e383d20d9d"> #### With product documentation installed <img width="718" alt="Screenshot 2024-10-10 at 09 55 38" src="https://github.com/user-attachments/assets/805ea4ca-8bc9-4355-a434-0ba81f8228a9"> --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Alex Szabo <[email protected]> Co-authored-by: Matthias Wilhelm <[email protected]> Co-authored-by: Elastic Machine <[email protected]>

sorenlouv · 2024-11-29T10:50:27Z

...infra/product_doc_base/server/services/inference_endpoint/utils/wait_until_model_deployed.ts

+  throw new Error(`Timeout waiting for ML model ${modelId} to be deployed`);
+};
+
+const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));


A little late but any reason why you opted for custom retry logic instead of p-retry? Same for waitUntilTaskCompleted

## Summary Follow-up of #194379. Turns out, the prefix for kibana system indices is `.kibana_*`, so our indices were not considered as kibana system indices and causing warnings when created, such as ``` Elasticsearch deprecation: 299 Elasticsearch-6db572c986d7e114b8b46f1d6f4169bed06717c5 "index name [.kibana-ai-product-doc-kibana] starts with a dot '.', in the next major version, index names starting with a dot are reserved for hidden indices and system indices" Origin:kibana ``` This PR addresses it, by changing the product doc index names to follow our system index pattern.

## Summary Follow-up of elastic#194379. Turns out, the prefix for kibana system indices is `.kibana_*`, so our indices were not considered as kibana system indices and causing warnings when created, such as ``` Elasticsearch deprecation: 299 Elasticsearch-6db572c986d7e114b8b46f1d6f4169bed06717c5 "index name [.kibana-ai-product-doc-kibana] starts with a dot '.', in the next major version, index names starting with a dot are reserved for hidden indices and system indices" Origin:kibana ``` This PR addresses it, by changing the product doc index names to follow our system index pattern. (cherry picked from commit d5cf0a6)

## Summary Close elastic#193473 Close elastic#193474 This PR utilize the documentation packages that are build via the tool introduced by elastic#193847, allowing to install them in Kibana and expose documentation retrieval as an LLM task that AI assistants (or other consumers) can call. Users can now decide to install the Elastic documentation from the assistant's config screen, which will expose a new tool for the assistant, `retrieve_documentation` (only implemented for the o11y assistant in the current PR, shall be done for security as a follow up). For more information, please refer to the self-review. ## General architecture <img width="1118" alt="Screenshot 2024-10-17 at 09 22 32" src="https://github.com/user-attachments/assets/3df8c30a-9ccc-49ab-92ce-c204b96d6fc4"> ## What this PR does Adds two plugin: - `productDocBase`: contains all the logic related to product documentation installation, status, and search. This is meant to be a "low level" components only responsible for this specific part. - `llmTasks`: an higher level plugin that will contain various LLM tasks to be used by assistants and genAI consumers. The intent is not to have a single place to put all llm tasks, but more to have a default place where we can introduce new tasks from. (fwiw, the `nlToEsql` task will probably be moved to that plugin). - Add a `retrieve_documentation` tool registration for the o11y assistant - Add a component on the o11y assistant configuration page to install the product doc (wiring the feature to the o11y assistant was done for testing purposes mostly, any addition / changes / enhancement should be done by the owning team - either in this PR or as a follow-up) ## What is NOT included in this PR: - Wire product base feature to the security assistant (should be done by the owning team as a follow-up) - installation - utilization as tool - FTR tests: this is somewhat blocked by the same things we need to figure out for elastic/kibana-team#1271 ## Screenshots ### Installation from o11y assistant configuration page <img width="1476" alt="Screenshot 2024-10-17 at 09 41 24" src="https://github.com/user-attachments/assets/31daa585-9fb2-400a-a2d1-5917a262367a"> ### Example of output #### Without product documentation installed <img width="739" alt="Screenshot 2024-10-10 at 09 59 41" src="https://github.com/user-attachments/assets/993fb216-6c9a-433f-bf44-f6e383d20d9d"> #### With product documentation installed <img width="718" alt="Screenshot 2024-10-10 at 09 55 38" src="https://github.com/user-attachments/assets/805ea4ca-8bc9-4355-a434-0ba81f8228a9"> --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Alex Szabo <[email protected]> Co-authored-by: Matthias Wilhelm <[email protected]> Co-authored-by: Elastic Machine <[email protected]>

## Summary Follow-up of elastic#194379. Turns out, the prefix for kibana system indices is `.kibana_*`, so our indices were not considered as kibana system indices and causing warnings when created, such as ``` Elasticsearch deprecation: 299 Elasticsearch-6db572c986d7e114b8b46f1d6f4169bed06717c5 "index name [.kibana-ai-product-doc-kibana] starts with a dot '.', in the next major version, index names starting with a dot are reserved for hidden indices and system indices" Origin:kibana ``` This PR addresses it, by changing the product doc index names to follow our system index pattern.

Create knowledge base registry plugin

76e3984

This was referenced Sep 30, 2024

[KB] add KB support to fleet package spec and implementation #193849

Closed

[fleet] Add support for knowledge base installation #194209

Draft

pgayvallet added release_note:skip Skip the PR/issue when compiling release notes v9.0.0 v8.16.0 Team:AI Infra AppEx AI Infrastructure Team labels Sep 30, 2024

pgayvallet and others added 4 commits September 30, 2024 10:11

run bootstrap

89e033c

[CI] Auto-commit changed files from 'node scripts/generate codeowners'

b3c67ee

[CI] Auto-commit changed files from 'node scripts/notice'

3dc368e

Add knowledge_base_entry SO type

54430dd

pgayvallet marked this pull request as ready for review September 30, 2024 11:18

pgayvallet requested a review from a team as a code owner September 30, 2024 11:18

pgayvallet added the backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) label Sep 30, 2024

afharo approved these changes Sep 30, 2024

View reviewed changes

make this empty plugin work, maybe?

7694e75

pgayvallet requested a review from a team as a code owner October 1, 2024 13:14

jbudz approved these changes Oct 1, 2024

View reviewed changes

pgayvallet and others added 7 commits October 1, 2024 15:54

fix SO meta

e7c482f

move attributes to server folder

763dad5

some tsdoc

596b036

[CI] Auto-commit changed files from 'node scripts/check_mappings_upda…

b3097df

…te --fix'

[CI] Auto-commit changed files from 'node scripts/jest_integration -u…

dac2b40

… src/core/server/integration_tests/ci_checks'

add new type to list

65cc3e7

Merge remote-tracking branch 'upstream/main' into kbn-193849-add-kb-r…

586e30f

…egistry-plugin

pgayvallet marked this pull request as draft October 3, 2024 13:26

pgayvallet added 2 commits October 3, 2024 15:26

installer: WIP

febae38

add plugin config

1f831e1

pgayvallet and others added 2 commits November 14, 2024 14:57

Merge remote-tracking branch 'upstream/main' into kbn-193849-add-kb-r…

75da6ea

…egistry-plugin

[CI] Auto-commit changed files from 'make api-docs'

1ddad2f

legrego added the ci:cloud-deploy Create or update a Cloud deployment label Nov 14, 2024

legrego approved these changes Nov 14, 2024

View reviewed changes

fix type in test

7063ce4

pgayvallet added 4 commits November 18, 2024 08:09

Merge remote-tracking branch 'upstream/main' into kbn-193849-add-kb-r…

c5c9d76

…egistry-plugin

update doc

a34e114

check status after installation

b9145ef

remove unused return type

040956d

pgayvallet mentioned this pull request Nov 18, 2024

[Discuss] Should we extend the purpose of the migrator node? #187312

Open

Merge branch 'main' into kbn-193849-add-kb-registry-plugin

09f8b2d

pgayvallet enabled auto-merge (squash) November 19, 2024 12:40

pgayvallet merged commit 455c781 into elastic:main Nov 19, 2024
41 checks passed

pgayvallet mentioned this pull request Nov 19, 2024

[8.x] [LLM tasks] Add product documentation retrieval task (#194379) #200754

Merged

pgayvallet mentioned this pull request Nov 29, 2024

[product documentation] Fix index names #202265

Merged

sorenlouv reviewed Nov 29, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[LLM tasks] Add product documentation retrieval task #194379

[LLM tasks] Add product documentation retrieval task #194379

pgayvallet commented Sep 30, 2024 •

edited by kibanamachine

Loading

elasticmachine commented Sep 30, 2024

afharo left a comment

jbudz left a comment

pgayvallet commented Oct 3, 2024

legrego left a comment

legrego Nov 14, 2024

pgayvallet Nov 15, 2024

mikecote Nov 18, 2024 •

edited

Loading

legrego Nov 14, 2024

legrego Nov 14, 2024

pgayvallet Nov 15, 2024

pgayvallet Nov 18, 2024

legrego Nov 18, 2024

pgayvallet commented Nov 15, 2024 •

edited

Loading

pgayvallet commented Nov 19, 2024

elasticmachine commented Nov 19, 2024 •

edited

Loading

API count

ESLint disabled in files

Total ESLint disabled count

kibanamachine commented Nov 19, 2024

kibanamachine commented Nov 19, 2024

pgayvallet commented Nov 19, 2024

sorenlouv Nov 29, 2024

[LLM tasks] Add product documentation retrieval task #194379

[LLM tasks] Add product documentation retrieval task #194379

Conversation

pgayvallet commented Sep 30, 2024 • edited by kibanamachine Loading

Summary

General architecture

What this PR does

What is NOT included in this PR:

Screenshots

Installation from o11y assistant configuration page

Example of output

Without product documentation installed

With product documentation installed

elasticmachine commented Sep 30, 2024

afharo left a comment

Choose a reason for hiding this comment

jbudz left a comment

Choose a reason for hiding this comment

pgayvallet commented Oct 3, 2024

legrego left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mikecote Nov 18, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

pgayvallet commented Nov 15, 2024 • edited Loading

pgayvallet commented Nov 19, 2024

elasticmachine commented Nov 19, 2024 • edited Loading

💚 Build Succeeded

Metrics [docs]

Module Count

Public APIs missing comments

Async chunks

Public APIs missing exports

Page load bundle

Saved Objects .kibana field count

API count

ESLint disabled in files

Total ESLint disabled count

History

kibanamachine commented Nov 19, 2024

kibanamachine commented Nov 19, 2024

💔 All backports failed

Manual backport

Questions ?

pgayvallet commented Nov 19, 2024

💚 All backports created successfully

Questions ?

Choose a reason for hiding this comment

pgayvallet commented Sep 30, 2024 •

edited by kibanamachine

Loading

mikecote Nov 18, 2024 •

edited

Loading

pgayvallet commented Nov 15, 2024 •

edited

Loading

elasticmachine commented Nov 19, 2024 •

edited

Loading