Skip to content

[8.19] [AI Infra] Fix inference id missing LLM task retrieval documentation function (#228009)#228422

Merged
qn895 merged 10 commits intoelastic:8.19from
qn895:backport/8.19/pr-228009
Jul 23, 2025
Merged

[8.19] [AI Infra] Fix inference id missing LLM task retrieval documentation function (#228009)#228422
qn895 merged 10 commits intoelastic:8.19from
qn895:backport/8.19/pr-228009

Conversation

@qn895
Copy link
Member

@qn895 qn895 commented Jul 17, 2025

Backport

This will backport the following commits from main to 8.19:

Questions ?

Please refer to the Backport tool documentation

…function (elastic#228009)

This PR addresses elastic#227906 and
fixes Inference id missing LLM task retrieval documentation function. By
default, it will use the default ELSER endpoint.

With the E5 model:

<img width="1410" height="881" alt="Screenshot 2025-07-15 at 08 10 40"
src="https://github.com/user-attachments/assets/43813d8e-011d-4a64-86cc-0e03e93c4c7f"
/>

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

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.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co>
(cherry picked from commit 03bb564)
@qn895 qn895 added the backport This PR is a backport of another PR label Jul 17, 2025
@qn895 qn895 requested a review from kibanamachine as a code owner July 17, 2025 10:48
@qn895 qn895 enabled auto-merge (squash) July 17, 2025 10:48
Copy link
Member

@jgowdyelastic jgowdyelastic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@qn895
Copy link
Member Author

qn895 commented Jul 18, 2025

@elasticmachine merge upstream

@qn895
Copy link
Member Author

qn895 commented Jul 23, 2025

@elasticmachine merge upstream

@qn895 qn895 merged commit cc3822f into elastic:8.19 Jul 23, 2025
8 checks passed
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

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
llmTasks 2 4 +2
Unknown metric groups

API count

id before after diff
llmTasks 25 27 +2

History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants