UX Improvement for charts with APM Metrics

[wchaparro]

Kibana version:
Present on Serverless dashboards. based on release dashboard,
AWS
us-east-1
2570872

Elasticsearch version:
elasticsearch-serverless
Server OS version:
n/a
Browser version:
Chrome Version 124.0.6367.207 (Official Build) (x86_64)
Browser OS version:
macOS 14.5 (23F79)
Original install method (e.g. download page, yum, from source, etc.):
n/a
Describe the bug:
We have a couple serverless dashboards that are gathering data from APM metrics. We've found that push based metrics are only created when the event actually triggers. This leads to charts that display an error like "Field es.breaker.trip.total was not found."
So this isn't really a "bug", but the user experience could be improved. We initially launched an investigation thinking that something was wrong with our charts or that the field names had changed.

Steps to reproduce:

1. Create a chart with APM push based metrics
2. see the error in the bottom left corner, if no metrics are produced

Please reach out to ES team if reproduction help is needed.

Expected behavior:
No error should be present. if no events are present
Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/kibana-visualizations (Team:Visualizations)

[dej611]

Duplicate of #151526

[teresaalvarezsoler]

@wchaparro I'm closing this one because we are already adressing this problem in the issue linked above. We are allowing solutions to customize error messages and format. There is a draft PR that you can test #184985

[markov00]

hey @teresaalvarezsoler The proposed solution works, as you described, in each application with an embedded Lens configured appropriately. It doesn't work by default on Dashboard as it seems described here.
I believe we need to discuss also with @elastic/kibana-presentation and understand when/how we can enable such configuration in dashboards