This change suggest a standard API definition to query telemetry data stored in any observability backend platform, both open source (Jaeger, Tempo, Zipkin, etc.) and proprietary (Datadog, appdynamics, etc.)
:x: The commit (14745e4171281911e043bb66abb79c96fcbae7e3, 036fd0cda0251f37d4c34501960bf2c3c9a224b2, 03974e068edb9fb49cbc0ba94590c7719f041d43, 02a3af8493ce4b513b6b50ccd06ecd9dcc1ae8fc, 824ae54edc986b080964dd0e1b259b75a6536244, dc0d11d80aab8a290b4299fd159b126a4a33b8e9, fefda77b50b1d424a6bf145faa9d46febe95aadc, b5b24a5b575b967bae24ae3d9e8a49fc281b1934, b8d6cd2a2cb43df020e2951536cb12138074f8c7, b41b1c5fcda0eb4b7b763e50898e9a28b6cf5766, 0ebf650cd9d9af1c9a8741cc088d5022a817ab0d, 539f296f53fd82f606622648f7ab2399844354fc, 08bf2808c3669053a4092689608969fe0c94558f, 2125d72c4c5bb205f839559696df7d099625bebf, ca5e32801ca592a49a08ad020c6cc23bc3795d54, 237ce540ad3456ee17fca952ef62117674d09dd2, 2b2bb0e2be065393ee0b4d1907c18dd43f7eee57, cc3aacc0c1d159c43e8061623503663fc655f748, 64b8a5de3bdd2b7f3e064c3b105049a35fb1ff66, ac9c16f2473684de038bb30d908b0d3d5d0c6e03, cf42b6a25afbb2d3d0154c8ff29d7413e6a9e41a, 57cf9a5efc6ce74a0dffe82f32c3a8d8a0c5ff0b). This user is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve.For further assistance with EasyCLA, please submit a support request ticket.
Standard Telemetry Data Query API
This change suggest a standard API definition to query telemetry data stored in any observability backend platform, both open source (Jaeger, Tempo, Zipkin, etc.) and proprietary (Datadog, appdynamics, etc.)
This idea of "having a standard for trace query API " has also been discussed by @lucasponce and others at length in https://github.com/open-telemetry/oteps/issues/193.
Collaborators and Reviewers: @ronyis @lucasponce
Comments, ideas, feedback, etc. are all very welcome and highly appreciated!