document migration of metrics from classic APM agent #960
Description
While we do provide and maintain dashboards for the JVM runtime metrics, this does not help migrating users that are using custom "content" (dashboards, alerts, ...), for example when:
- building custom dashboards on JVM runtime metrics
- using custom metrics, or metrics captured through a bridge API like Micrometer or OpenTelemetry API
This applies to all of the following metrics:
- JVM runtime metrics
- Micrometer metrics
- OpenTelemetry SDK metrics (through OTel bridge)
For each of those, we should be able to provide:
- an alternative metric name or ESQL query if such exists
- an identified gap when there is no alternative
- link to a configuration option if necessary (for example with EDOT we do enable by default some of the JVM metrics, this would not
For simplicity, this documentation should aim to focus on the "otel-native" data storage, not the ECS mapping used by APM server. Also, we should write this documentation to make it relevant for both EDOT and upstream instrumentation/SDK.