Kibana version:
8.17.2
Elasticsearch version:
8.17.2
Server OS version:
Browser version:
Latest Chrome
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Cloud
Describe the bug:
When asking the assistant to extract data from an index with custom field names that require escaping it is using the wrong escape mechanisms.
E.g. site-name would require site-name but it uses "site-name"
Steps to reproduce:
- Create an index with non standard field name mapping like "site-name" or "Total Bytes"
- Ask the o11y AI assistant to analyze data thats in those fields.
- Assistant will create wrong ES|QL and retries until it may find the right way
Expected behavior:
Assistant can create correct ES|QL also for non standard field names and execute the created query successfully.
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
Kibana version:
8.17.2
Elasticsearch version:
8.17.2
Server OS version:
Browser version:
Latest Chrome
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Cloud
Describe the bug:
When asking the assistant to extract data from an index with custom field names that require escaping it is using the wrong escape mechanisms.
E.g. site-name would require
site-namebut it uses "site-name"Steps to reproduce:
Expected behavior:
Assistant can create correct ES|QL also for non standard field names and execute the created query successfully.
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: