Compatibility with Elasticsearch APM UI

[jozef-slezak]

Requirement - what kind of business use case are you trying to solve?

Storing to Elastic Search backend in the way that Kibana APM UI can display spans.
https://www.elastic.co/guide/en/apm/get-started/current/distributed-tracing.html

Problem - what in Jaeger blocks you from solving the requirement?

It is more like an improvement rather than a blocking issue... (that might lead to a synergy between Jaeger and ELK).

Proposal - what do you suggest to solve the problem or improve the existing situation?

Use the same/similar data model as https://github.com/elastic/apm-server when storing data to ELK.

Any open questions to address

[yurishkuro]

Better links:

• https://www.elastic.co/guide/en/apm/get-started/current/overview.html
• https://www.elastic.co/guide/en/apm/get-started/current/apm-data-model.html

Jaeger does not have anything that maps to E-APM's "transactions" (similar to "segments" in other APM solutions)

[pavolloffay]

We don't have plans to support this at the moment. This could be done externally with a storage plugin #638

[yurishkuro]

doesn't look like this is getting traction, closing