Unable to add Latency threshold alert rule due to error

[maretodoric]

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.

Error: Cannot read properties of undefined (reading 'eui')
    at f (https://xxx/afbd904e868f/bundles/plugin/apm/1.0.0/apm.chunk.14.js:3:18120)
    at la (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:59212)
    at ec (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:114853)
    at Pc (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:99736)
    at Nc (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:99563)
    at Dc (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:99396)
    at wc (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:96239)
    at https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:45140
    at t.unstable_runWithPriority (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:433:3768)
    at Xo (https://xxx/afbd904e868f/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:425:44917)

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:

[dmlemeshko]

I'm not able to reproduce it on Elastic Cloud deployment 8.14.1

but maybe it is an issue with specific distro.

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[maretodoric]

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.

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[maryam-saeidi]

Seems related to https://github.com/elastic/kibana/issues/186969 (PR)

[maryam-saeidi]

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.