[RAM] Kibana CDN

[XavierM]

We need to test:

• [x] rule management page @umbopepato
• [x] rule logs page @umbopepato
• [x] rule details @umbopepato
• [x] rule fly-out (make sure that all the rule params is working so click on every rule types) @XavierM
• [x] connector page @JiaweiWu
• [x] connector fly-out @JiaweiWu
• [x] maintenance window @JiaweiWu

Details

Each team with UI in a serverless solution create a new serverless project in QA. Only QA is currently configured to load assets from the CDN.

Interact with critical paths through your UI

Keep your network tab open to ensure asset loading and JS initiated requests work as expected

If you have JS code in the browser that is calling domains other than origin or *.elastic.co please reach out to us, your requests will be blocked!

Report any issues to #kibana-core

Additional info about which assets loaded from the CDN:

JavaScript bundles (majority of requests on first load)

All plugin JS bundles

Includes SASS or CSS modules imported into code

All SVGs, PNGs or other supported file types imported into code

Monaco editor

Core bundles

…and more

Any assets living under /public/assets

EUI’s CSS bundles

Favicons

Fonts

[elasticmachine]

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

[JiaweiWu]

Connectors Page

UI

Assets

Connectors Flyout

Maintenance Window

UI

Assets

Everything looks to be working as expected

[umbopepato]

Rules page ✅

Rule details page ✅

Rule details (logs) ✅

No network errors found (tested with all stack rule types)

[XavierM]

Anomaly detection ✅

APM Anomaly ✅

Custom threshold ✅

Elasticsearch query KQL ✅ / DSL ✅

Error count threshold ✅

Failed transaction rate threshold ✅

Inventory ✅

Latency threshold ✅

SLO burn rate ✅

[XavierM]

Done!