Log Elasticsearch queries in user journeys

[ablnk]

• [x] Querying aggregated data from K8S for Serverless | https://github.com/elastic/oblt-playwright/commit/97c8c985005e9d15d8b77c842ca31c75998d315e
• [x] Querying aggregated data from K8S for ESS | https://github.com/elastic/oblt-playwright/commit/1f4d8c26687c2d9159b27b6646b52f6b531bcb42
• [x] Infrastructure Monitoring for Serverless | https://github.com/elastic/oblt-playwright/commit/552565e554dfdfa63e7e1718b811b9fbf69f8a51
• [x] Infrastructure Monitoring for ESS | https://github.com/elastic/oblt-playwright/commit/57e18e291ae52949f88add6a260f0bc652596f9b
• [ ] APM for Serverless
• [ ] APM for ESS

[ablnk]

@cachedout Unlike Infrastructure UI, APM UI doesn't allow you to inspect visualizations, from where you can get the actual Elasticsearch query.

APM:

Infra:

You can trace slow Elasticsearch query to the origin via shard level slow search log (which is out of Playwright's scope), with certain limitations though:

At the moment, Kibana can only highlight cases where a slow query originated from a Kibana visualization, Lens, Discover, Maps, or Alerting.