Kibana version:
Kibana v8.13.3
Elasticsearch version:
ES v8.13.3
Server OS version:
CentOS Linux release 7.4.1708 (Core)
Browser version:
Google Chrome 127.0.6533.73 64
Browser OS version:
Windows 11
Original install method (e.g. download page, yum, from source, etc.):
download page
Describe the bug:
I couldn't see Heap memory pools in JVM metrics when I was testing APM server. Kibana shows that "Reduced time range can only be used with a specified default time field on the data view. Either use a different data view with default time field or remove the reduced time range from Committed [bytes]." All other metrics are displayed normally
Steps to reproduce:
1.Observerability -> APM -> Services ->"my-service" -> Metrics I couldn't see Heap memory pools in JVM metrics
I copy to dashboard and updata Data View , then it's ok!!!!!
I'm sure of the field jvm.memory.heap.pool.used
Expected behavior:
Expectation helps me recover it
Screenshots (if relevant):
Kibana version: Kibana v8.13.3 Elasticsearch version: ES v8.13.3 Server OS version: CentOS Linux release 7.4.1708 (Core) Browser version: Google Chrome 127.0.6533.73 64 Browser OS version: Windows 11 Original install method (e.g. download page, yum, from source, etc.): download page Describe the bug: I couldn't see Heap memory pools in JVM metrics when I was testing APM server. Kibana shows that "Reduced time range can only be used with a specified default time field on the data view. Either use a different data view with default time field or remove the reduced time range from Committed [bytes]." All other metrics are displayed normally Steps to reproduce: 1.Observerability -> APM -> Services ->"my-service" -> Metrics I couldn't see Heap memory pools in JVM metrics
Expected behavior: Expectation helps me recover it Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context: