Closed maretodoric closed 1 week ago
I'm not able to reproduce it on Elastic Cloud deployment 8.14.1
but maybe it is an issue with specific distro.
Pinging @elastic/response-ops (Team:ResponseOps)
I'd like to point out that this elasticsearch/kibana cluster is hosted on a DMZ. Proxy is added to reach artifacts.elastic.co, for fleet to work. If this feature is also dependent on internet connection, this could be the cause.
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
Seems related to https://github.com/elastic/kibana/issues/186969 (PR)
Fixed in https://github.com/elastic/kibana/pull/188724, and the fix is available from v8.15.
For now, the workaround is to create/update APM rules using observability > alerts > rules page.
Kibana version: 8.14.1
Elasticsearch version: 8.14.1
Server OS version: RHEL 9
Browser version: Google Chrome 120.0.6099.200
Browser OS version: Windows 10
Original install method (e.g. download page, yum, from source, etc.): From compressed tarball
Describe the bug: When attempting to add new Latency threshold Alert Rule (Stack Management -> Alerts and Insights -> Rules -> Create Rule -> Latency threshold (APM and User Experience)), i dialog window opens and i get an error message below "Latency threshold" header.
I have another elk cluster running on version 8.9.1 but there i get the screen to select "Service", "Environment", "When", "Type", "Name" etc.
Steps to reproduce: Described above
Expected behavior: Should display screen to select "Service", "Environment", "When", "Type", "Name" etc.
Screenshots (if relevant):
Errors in browser console (if relevant): Same as error described above
Provide logs and/or server output (if relevant): Nothing similar appears in server log.
Any additional context: