In order to observe driver operations (metrics, tracing), one needs to start request (Statement) observation before calling the driver (execute, prepare) methods. RequestTracker provides a good callback to obtain a notification on when a statement has completed.
However, RequestTracker does not provide callback hooks for request start and it does not call onSuccess/onError methods for statement preparation.
Ideally, RequestTracker would provide a onStart method and perform callbacks for prepare calls.
Also, page continuation requests and transparent re-prepare events cannot be observed through an external instrumentation.
References on how observability instrumentation currently looks like:
Pre-execute/pre-prepare code:
Observation completion through RequestTracker:
Could you consider updating the RequestTracker API so that it is usable for observability instrumentation?
Environment
None
Pull Requests
None
Activity
Erick Ramirez
October 26, 2022 at 1:54 PM
Thanks for logging this feature request. It looks useful for developers. I’ll socialise it with the other contributors and I just wanted to acknowledge it. Cheers!
Major
In order to observe driver operations (metrics, tracing), one needs to start request (Statement) observation before calling the driver (execute, prepare) methods. RequestTracker provides a good callback to obtain a notification on when a statement has completed.
However, RequestTracker does not provide callback hooks for request start and it does not call onSuccess/onError methods for statement preparation.
Ideally, RequestTracker would provide a onStart method and perform callbacks for prepare calls.
Also, page continuation requests and transparent re-prepare events cannot be observed through an external instrumentation.
References on how observability instrumentation currently looks like:
Pre-execute/pre-prepare code:
Observation completion through RequestTracker:
Could you consider updating the RequestTracker API so that it is usable for observability instrumentation?