Grafana provides support for Tempo's Trace view, but Tempo can only store data reported by Jaeger and OTLP.
Currently, all our APM Trace work is completed based on ES APM. Migrating APM to Jaeger or OTLP means a huge workload, such as environment changes and code changes. At the same time, OTLP is still in an iterative and unstable state, such as PHP's OTLP interface. Migration means code changes and PHP version updates, which will be a long process.
My organization has completed the migration of logs and indicators to LOKI and Prometheus, and combined it with Grafana for observability work. However, based on the above problems, we are still in a wait-and-see state regarding the migration to OTLP/Tempo.
We still hope to complete the observability work of logs, indicators, and Trace based on Grafana, so we hope to add support for Trace views of Elastic APM data sources, just like Tempo. We believe that such improvements can attract more organizations to switch to Grafana-based observability, because the transformation of Trace is the most complex part of the three.