+1. Side note - we must introduce a community process to prevent such hardly maintained APIs from the project, in the first place.
вт, 7 июл. 2026 г. в 18:40, Mikhail Petrov <[email protected]>: > > Igniters, > I would like to initiate a discussion on the deprecation and removal of > Ignite Tracing. > Motivation > 1.Ignite Tracing implementation is based on OpenCensus, which is no > longer maintained. [1] > 2.Ignite Tracing implementation is still not production-ready. It is > difficult to configure and, in some cases, introduces significant > performance overhead. > 3.Ignite Tracing handles asynchronous Ignite operations poorly, making > the resulting traces difficult to interpret. > 4.Ignite Tracing implementation is tightly coupled with the > Communication and Discovery subsystems, which complicates their > maintenance and refactoring. > 5.Ignite Tracing has not been maintained for more than three years. > Are there any known examples of real customers successfully using Ignite > Tracing? > Alternatives > 1.Ignite Performance Statistics [2] [3] > 2.Ignite Metric System [4] > 3.Ignite System Views [5] > The aforementioned mechanisms are actively maintained and serve as the > primary means of monitoring Ignite. > WDYT? > > Regards, > Mikhail. > > [1] https://opentelemetry.io/blog/2023/sunsetting-opencensus > [2] > https://ignite.apache.org/docs/ignite2/latest/monitoring-metrics/performance-statistics > [3] > https://ignite.apache.org/docs/ignite2/latest/extensions-and-integrations/performance-statistics#print-statistics > [4] > https://ignite.apache.org/docs/ignite2/latest/monitoring-metrics/new-metrics-system > [5] > https://ignite.apache.org/docs/ignite2/latest/monitoring-metrics/system-views >
