[AI Infra] Updates NL-2-ESQL docs#224868
Merged
qn895 merged 10 commits intoelastic:mainfrom Jun 24, 2025
Merged
Conversation
Member
Author
|
@elasticmachine merge upstream |
Contributor
|
Pinging @elastic/ml-ui (:ml) |
Member
Author
|
@elasticmachine merge upstream |
Member
Author
|
@elasticmachine merge upstream |
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
Jun 25, 2025
## Summary This PR pulls the latest changes from the Elasticsearch's ES|QL documentation updates the ESQL docs. It also adds new ES|QL docs for: - KQL - TO_DATE_NANOS Test results: ``` Model gpt-4o scored 27.700000000000003 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 12 out of 13 - category: ES|QL query generation - scored 12.200000000000003 out of 13 - category: SPL to ESQL - scored 3.5 out of 4 ------------------------------------------- Model gpt-4o scored 25.300000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 10.3 out of 13 - category: ES|QL query generation - scored 11.500000000000002 out of 13 - category: SPL to ESQL - scored 3.5 out of 4 ------------------------------------------- ------------------------------------------- Model gpt-4o scored 26.300000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 10.8 out of 13 - category: ES|QL query generation - scored 11.700000000000003 out of 13 - category: SPL to ESQL - scored 3.8 out of 4 Model gpt-4o scored 27.500000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 12 out of 13 - category: ES|QL query generation - scored 11.700000000000003 out of 13 - category: SPL to ESQL - scored 3.8 out of 4 ``` ### Checklist 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) ### Identify 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
9 tasks
kibanamachine
added
the
backport missing
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
7 similar comments
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Member
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
qn895
added a commit
to qn895/kibana
that referenced
this pull request
Jul 9, 2025
## Summary This PR pulls the latest changes from the Elasticsearch's ES|QL documentation updates the ESQL docs. It also adds new ES|QL docs for: - KQL - TO_DATE_NANOS Test results: ``` Model gpt-4o scored 27.700000000000003 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 12 out of 13 - category: ES|QL query generation - scored 12.200000000000003 out of 13 - category: SPL to ESQL - scored 3.5 out of 4 ------------------------------------------- Model gpt-4o scored 25.300000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 10.3 out of 13 - category: ES|QL query generation - scored 11.500000000000002 out of 13 - category: SPL to ESQL - scored 3.5 out of 4 ------------------------------------------- ------------------------------------------- Model gpt-4o scored 26.300000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 10.8 out of 13 - category: ES|QL query generation - scored 11.700000000000003 out of 13 - category: SPL to ESQL - scored 3.8 out of 4 Model gpt-4o scored 27.500000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 12 out of 13 - category: ES|QL query generation - scored 11.700000000000003 out of 13 - category: SPL to ESQL - scored 3.8 out of 4 ``` ### Checklist 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) ### Identify 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit dd29b09)
qn895
added a commit
that referenced
this pull request
Jul 9, 2025
# Backport This will backport the following commits from `main` to `8.19`: - [[AI Infra] Update NL-2-ESQL docs (#224868)](#224868) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-24T23:17:52Z","message":"[AI Infra] Update NL-2-ESQL docs (#224868)\n\n## Summary\n\nThis PR pulls the latest changes from the Elasticsearch's ES|QL\ndocumentation updates the ESQL docs. It also adds new ES|QL docs for:\n- KQL\n- TO_DATE_NANOS\n\nTest results:\n\n```\nModel gpt-4o scored 27.700000000000003 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 12 out of 13\n- category: ES|QL query generation - scored 12.200000000000003 out of 13\n- category: SPL to ESQL - scored 3.5 out of 4\n-------------------------------------------\n\nModel gpt-4o scored 25.300000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 10.3 out of 13\n- category: ES|QL query generation - scored 11.500000000000002 out of 13\n- category: SPL to ESQL - scored 3.5 out of 4\n-------------------------------------------\n-------------------------------------------\n\nModel gpt-4o scored 26.300000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 10.8 out of 13\n- category: ES|QL query generation - scored 11.700000000000003 out of 13\n- category: SPL to ESQL - scored 3.8 out of 4\n\n\nModel gpt-4o scored 27.500000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 12 out of 13\n- category: ES|QL query generation - scored 11.700000000000003 out of 13\n- category: SPL to ESQL - scored 3.8 out of 4\n\n\n```\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dd29b099295ee449b88d174107e1e6544643accd","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","backport missing","Team:ML","backport:version","v9.1.0","v9.2.0"],"title":"[AI Infra] Update NL-2-ESQL docs","number":224868,"url":"https://github.com/elastic/kibana/pull/224868","mergeCommit":{"message":"[AI Infra] Update NL-2-ESQL docs (#224868)\n\n## Summary\n\nThis PR pulls the latest changes from the Elasticsearch's ES|QL\ndocumentation updates the ESQL docs. It also adds new ES|QL docs for:\n- KQL\n- TO_DATE_NANOS\n\nTest results:\n\n```\nModel gpt-4o scored 27.700000000000003 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 12 out of 13\n- category: ES|QL query generation - scored 12.200000000000003 out of 13\n- category: SPL to ESQL - scored 3.5 out of 4\n-------------------------------------------\n\nModel gpt-4o scored 25.300000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 10.3 out of 13\n- category: ES|QL query generation - scored 11.500000000000002 out of 13\n- category: SPL to ESQL - scored 3.5 out of 4\n-------------------------------------------\n-------------------------------------------\n\nModel gpt-4o scored 26.300000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 10.8 out of 13\n- category: ES|QL query generation - scored 11.700000000000003 out of 13\n- category: SPL to ESQL - scored 3.8 out of 4\n\n\nModel gpt-4o scored 27.500000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 12 out of 13\n- category: ES|QL query generation - scored 11.700000000000003 out of 13\n- category: SPL to ESQL - scored 3.8 out of 4\n\n\n```\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dd29b099295ee449b88d174107e1e6544643accd"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224868","number":224868,"mergeCommit":{"message":"[AI Infra] Update NL-2-ESQL docs (#224868)\n\n## Summary\n\nThis PR pulls the latest changes from the Elasticsearch's ES|QL\ndocumentation updates the ESQL docs. It also adds new ES|QL docs for:\n- KQL\n- TO_DATE_NANOS\n\nTest results:\n\n```\nModel gpt-4o scored 27.700000000000003 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 12 out of 13\n- category: ES|QL query generation - scored 12.200000000000003 out of 13\n- category: SPL to ESQL - scored 3.5 out of 4\n-------------------------------------------\n\nModel gpt-4o scored 25.300000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 10.3 out of 13\n- category: ES|QL query generation - scored 11.500000000000002 out of 13\n- category: SPL to ESQL - scored 3.5 out of 4\n-------------------------------------------\n-------------------------------------------\n\nModel gpt-4o scored 26.300000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 10.8 out of 13\n- category: ES|QL query generation - scored 11.700000000000003 out of 13\n- category: SPL to ESQL - scored 3.8 out of 4\n\n\nModel gpt-4o scored 27.500000000000004 out of 30\n-------------------------------------------\n-------------------------------------------\nModel gpt-4o scores per category\n- category: ES|QL commands and functions usage - scored 12 out of 13\n- category: ES|QL query generation - scored 11.700000000000003 out of 13\n- category: SPL to ESQL - scored 3.8 out of 4\n\n\n```\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"dd29b099295ee449b88d174107e1e6544643accd"}},{"branch":"9.2","label":"v9.2.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
kibanamachine
added
v8.19.0
and removed
backport missing
qn895
added a commit
that referenced
this pull request
Jul 10, 2025
## Summary Follow up of #224868. This PR fixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs not having ES|QL in the file name. ### Checklist 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) ### Identify 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
qn895
added a commit
to qn895/kibana
that referenced
this pull request
Jul 10, 2025
) ## Summary Follow up of elastic#224868. This PR fixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs not having ES|QL in the file name. ### Checklist 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) ### Identify 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit f7c3fe0)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 10, 2025
) ## Summary Follow up of elastic#224868. This PR fixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs not having ES|QL in the file name. ### Checklist 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) ### Identify 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit f7c3fe0)
kibanamachine
added a commit
that referenced
this pull request
Jul 10, 2025
…) (#227382) # Backport This will backport the following commits from `main` to `9.1`: - [[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)](#225382) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-07-10T08:47:36Z","message":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)\n\n## Summary\n\nFollow up of #224868. This PR\nfixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs\nnot having ES|QL in the file name.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"f7c3fe011767f128502ee62dc918eb041057240a","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","backport:version","Team:AI Infra","v9.1.0","v8.19.0","v9.2.0","v9.0.4"],"title":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs","number":225382,"url":"https://github.com/elastic/kibana/pull/225382","mergeCommit":{"message":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)\n\n## Summary\n\nFollow up of #224868. This PR\nfixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs\nnot having ES|QL in the file name.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"f7c3fe011767f128502ee62dc918eb041057240a"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19","9.0"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225382","number":225382,"mergeCommit":{"message":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)\n\n## Summary\n\nFollow up of #224868. This PR\nfixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs\nnot having ES|QL in the file name.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"f7c3fe011767f128502ee62dc918eb041057240a"}},{"branch":"9.0","label":"v9.0.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>
qn895
added a commit
that referenced
this pull request
Jul 10, 2025
) (#227379) # Backport This will backport the following commits from `main` to `8.19`: - [[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)](#225382) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-07-10T08:47:36Z","message":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)\n\n## Summary\n\nFollow up of #224868. This PR\nfixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs\nnot having ES|QL in the file name.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"f7c3fe011767f128502ee62dc918eb041057240a","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","backport:version","Team:AI Infra","v9.1.0","v8.19.0","v9.2.0","v9.0.4"],"title":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs","number":225382,"url":"https://github.com/elastic/kibana/pull/225382","mergeCommit":{"message":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)\n\n## Summary\n\nFollow up of #224868. This PR\nfixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs\nnot having ES|QL in the file name.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"f7c3fe011767f128502ee62dc918eb041057240a"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19","9.0"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225382","number":225382,"mergeCommit":{"message":"[AI Infra] Fix missing LOOKUP JOIN ES|QL command in docs (#225382)\n\n## Summary\n\nFollow up of #224868. This PR\nfixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs\nnot having ES|QL in the file name.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"f7c3fe011767f128502ee62dc918eb041057240a"}},{"branch":"9.0","label":"v9.0.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
kertal
pushed a commit
to kertal/kibana
that referenced
this pull request
Jul 25, 2025
) ## Summary Follow up of elastic#224868. This PR fixes missing LOOKUP JOIN ES|QL command in docs due to the built-docs not having ES|QL in the file name. ### Checklist 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) ### Identify 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
pgayvallet
added a commit
that referenced
this pull request
Sep 18, 2025
## Summary Cleanup the prompts of the NL-2-ESQL task - adapt the instructions based on the [ML experiment](https://github.com/elastic/nl2esql/tree/main) - remove parts of the doc which aren't really useful in any way (e.g how to use ES|QL with Kibana) - use nl->esql examples instead of examples describing what each request does (more efficient according to the experiment) ### Numbers First call (`request_documentation`): **+700 tokens**, explained by the fact that we now provide ES|QL examples to the LLM during this step, which can increase the selection efficiency. Second call (`generate_esql`): **-2300** tokens Overall, **-1600 input tokens**, which represent, depending on the rest of the input (e.g mappings or not) **-10% tokens** to **-20% tokens**, and better efficiency ### Evals **agent builder eval suite** | Dataset | Filter level | Factuality | Groundedness | Relevance | Sequence Accuracy | | :--- | :--- | :---: | :---: | :---: | :---: | | Analytical | **Baseline** | 36.7% | 68.3% | 82.1% | 100.0% | | Analytical | **PR** | 41.1% | 76.8% | 89.2% | 97.8% | (ran multiple time, quite stable). The better scores are likely caused by one or two less failing queries compared to the baseline. **inference plugin's esql eval suite** ``` Model openai-gpt4o scored 27.449999999999996 out of 31 ------------------------------------------- Model openai-gpt4o scores per category - category: ES|QL commands and functions usage - scored 11.8 out of 14 - category: ES|QL query generation - scored 12.200000000000001 out of 13 - category: SPL to ESQL - scored 3.45 out of 4 ------------------------------------------- ``` Which, compared to the last runs (done in #224868), confirms there's no regression, or maybe even some slight improvements **o11y ES|QL eval suite** (baseline from [this doc](https://docs.google.com/spreadsheets/d/1aHJHj8KALdTLVJxjoyI2VdqGBVzcJS7v2P7yJRmESZY/edit?gid=243046278#gid=243046278), evaluator was Gemini 2.5-pro for all candidates) | Dataset | Model | Baseline | Score | Delta | | :--- | :--- | :---: | :---: | :---: | | ESQL query generation | GPT4.1 | 147.5| 145.5 | **-2** | | ESQL query generation | Gemini 2.5-pro | 128.7| 132.25 | **+3.55** | | ESQL query generation | Claude 3.7 | 150 | 158.75 | **+8.75** |
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Sep 24, 2025
## Summary Cleanup the prompts of the NL-2-ESQL task - adapt the instructions based on the [ML experiment](https://github.com/elastic/nl2esql/tree/main) - remove parts of the doc which aren't really useful in any way (e.g how to use ES|QL with Kibana) - use nl->esql examples instead of examples describing what each request does (more efficient according to the experiment) ### Numbers First call (`request_documentation`): **+700 tokens**, explained by the fact that we now provide ES|QL examples to the LLM during this step, which can increase the selection efficiency. Second call (`generate_esql`): **-2300** tokens Overall, **-1600 input tokens**, which represent, depending on the rest of the input (e.g mappings or not) **-10% tokens** to **-20% tokens**, and better efficiency ### Evals **agent builder eval suite** | Dataset | Filter level | Factuality | Groundedness | Relevance | Sequence Accuracy | | :--- | :--- | :---: | :---: | :---: | :---: | | Analytical | **Baseline** | 36.7% | 68.3% | 82.1% | 100.0% | | Analytical | **PR** | 41.1% | 76.8% | 89.2% | 97.8% | (ran multiple time, quite stable). The better scores are likely caused by one or two less failing queries compared to the baseline. **inference plugin's esql eval suite** ``` Model openai-gpt4o scored 27.449999999999996 out of 31 ------------------------------------------- Model openai-gpt4o scores per category - category: ES|QL commands and functions usage - scored 11.8 out of 14 - category: ES|QL query generation - scored 12.200000000000001 out of 13 - category: SPL to ESQL - scored 3.45 out of 4 ------------------------------------------- ``` Which, compared to the last runs (done in elastic#224868), confirms there's no regression, or maybe even some slight improvements **o11y ES|QL eval suite** (baseline from [this doc](https://docs.google.com/spreadsheets/d/1aHJHj8KALdTLVJxjoyI2VdqGBVzcJS7v2P7yJRmESZY/edit?gid=243046278#gid=243046278), evaluator was Gemini 2.5-pro for all candidates) | Dataset | Model | Baseline | Score | Delta | | :--- | :--- | :---: | :---: | :---: | | ESQL query generation | GPT4.1 | 147.5| 145.5 | **-2** | | ESQL query generation | Gemini 2.5-pro | 128.7| 132.25 | **+3.55** | | ESQL query generation | Claude 3.7 | 150 | 158.75 | **+8.75** |
peteharverson
changed the title
niros1
pushed a commit
that referenced
this pull request
Sep 30, 2025
## Summary Cleanup the prompts of the NL-2-ESQL task - adapt the instructions based on the [ML experiment](https://github.com/elastic/nl2esql/tree/main) - remove parts of the doc which aren't really useful in any way (e.g how to use ES|QL with Kibana) - use nl->esql examples instead of examples describing what each request does (more efficient according to the experiment) ### Numbers First call (`request_documentation`): **+700 tokens**, explained by the fact that we now provide ES|QL examples to the LLM during this step, which can increase the selection efficiency. Second call (`generate_esql`): **-2300** tokens Overall, **-1600 input tokens**, which represent, depending on the rest of the input (e.g mappings or not) **-10% tokens** to **-20% tokens**, and better efficiency ### Evals **agent builder eval suite** | Dataset | Filter level | Factuality | Groundedness | Relevance | Sequence Accuracy | | :--- | :--- | :---: | :---: | :---: | :---: | | Analytical | **Baseline** | 36.7% | 68.3% | 82.1% | 100.0% | | Analytical | **PR** | 41.1% | 76.8% | 89.2% | 97.8% | (ran multiple time, quite stable). The better scores are likely caused by one or two less failing queries compared to the baseline. **inference plugin's esql eval suite** ``` Model openai-gpt4o scored 27.449999999999996 out of 31 ------------------------------------------- Model openai-gpt4o scores per category - category: ES|QL commands and functions usage - scored 11.8 out of 14 - category: ES|QL query generation - scored 12.200000000000001 out of 13 - category: SPL to ESQL - scored 3.45 out of 4 ------------------------------------------- ``` Which, compared to the last runs (done in #224868), confirms there's no regression, or maybe even some slight improvements **o11y ES|QL eval suite** (baseline from [this doc](https://docs.google.com/spreadsheets/d/1aHJHj8KALdTLVJxjoyI2VdqGBVzcJS7v2P7yJRmESZY/edit?gid=243046278#gid=243046278), evaluator was Gemini 2.5-pro for all candidates) | Dataset | Model | Baseline | Score | Delta | | :--- | :--- | :---: | :---: | :---: | | ESQL query generation | GPT4.1 | 147.5| 145.5 | **-2** | | ESQL query generation | Gemini 2.5-pro | 128.7| 132.25 | **+3.55** | | ESQL query generation | Claude 3.7 | 150 | 158.75 | **+8.75** |
rylnd
pushed a commit
to rylnd/kibana
that referenced
this pull request
Oct 17, 2025
## Summary Cleanup the prompts of the NL-2-ESQL task - adapt the instructions based on the [ML experiment](https://github.com/elastic/nl2esql/tree/main) - remove parts of the doc which aren't really useful in any way (e.g how to use ES|QL with Kibana) - use nl->esql examples instead of examples describing what each request does (more efficient according to the experiment) ### Numbers First call (`request_documentation`): **+700 tokens**, explained by the fact that we now provide ES|QL examples to the LLM during this step, which can increase the selection efficiency. Second call (`generate_esql`): **-2300** tokens Overall, **-1600 input tokens**, which represent, depending on the rest of the input (e.g mappings or not) **-10% tokens** to **-20% tokens**, and better efficiency ### Evals **agent builder eval suite** | Dataset | Filter level | Factuality | Groundedness | Relevance | Sequence Accuracy | | :--- | :--- | :---: | :---: | :---: | :---: | | Analytical | **Baseline** | 36.7% | 68.3% | 82.1% | 100.0% | | Analytical | **PR** | 41.1% | 76.8% | 89.2% | 97.8% | (ran multiple time, quite stable). The better scores are likely caused by one or two less failing queries compared to the baseline. **inference plugin's esql eval suite** ``` Model openai-gpt4o scored 27.449999999999996 out of 31 ------------------------------------------- Model openai-gpt4o scores per category - category: ES|QL commands and functions usage - scored 11.8 out of 14 - category: ES|QL query generation - scored 12.200000000000001 out of 13 - category: SPL to ESQL - scored 3.45 out of 4 ------------------------------------------- ``` Which, compared to the last runs (done in elastic#224868), confirms there's no regression, or maybe even some slight improvements **o11y ES|QL eval suite** (baseline from [this doc](https://docs.google.com/spreadsheets/d/1aHJHj8KALdTLVJxjoyI2VdqGBVzcJS7v2P7yJRmESZY/edit?gid=243046278#gid=243046278), evaluator was Gemini 2.5-pro for all candidates) | Dataset | Model | Baseline | Score | Delta | | :--- | :--- | :---: | :---: | :---: | | ESQL query generation | GPT4.1 | 147.5| 145.5 | **-2** | | ESQL query generation | Gemini 2.5-pro | 128.7| 132.25 | **+3.55** | | ESQL query generation | Claude 3.7 | 150 | 158.75 | **+8.75** |
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
4 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.
Summary
This PR pulls the latest changes from the Elasticsearch's ES|QL documentation updates the ESQL docs. It also adds new ES|QL docs for:
Test results:
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.