You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open Telemetry is a powerful serviceability framework which helps to gain insights into the performance and behaviour of the systems. It facilitates generation, collection, and management of telemetry data such as traces.
The OSS Presto already had a basic implementation of Open Telemetry #18534, which was an experimental feature, had a limited set of telemetry data (Query state changes) and did not include a child span concept.
This enhancement will make Presto more flexible, allowing support for both parent and child spans. Additionally, spans can now be propagated to the worker nodes as well.
The text was updated successfully, but these errors were encountered:
Please note that there is an SPI and engine integration and a plugin which integrates with OpenAPI. Can you describe the SPI and engine integration more thoroughly--for example, is there any change required to communicate span information in the worker back to the coordinator? Can you create an RFC for this design that outlines changes to the SPI, engine (communication for example of spans), and implementation of the Open Telemetry spec as a plugin?
Open Telemetry is a powerful serviceability framework which helps to gain insights into the performance and behaviour of the systems. It facilitates generation, collection, and management of telemetry data such as traces.
The OSS Presto already had a basic implementation of Open Telemetry #18534, which was an experimental feature, had a limited set of telemetry data (Query state changes) and did not include a child span concept.
This enhancement will make Presto more flexible, allowing support for both parent and child spans. Additionally, spans can now be propagated to the worker nodes as well.
The text was updated successfully, but these errors were encountered: