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
This feature could also be implemented via an SLTR query parameter instead of through the profile API setting.
Do you have any additional context?
Please let me know if there are alternative ways to debug the latency each feature adds to a query during feature logging already using the plugin, as I couldn't find any references in the official documentation
The text was updated successfully, but these errors were encountered:
@adamjq By convention, I believe the profile API will include latency in the profile field rather than the hits field. If we want to record the logging, can we create a logging schema that includes both necessary and optional fields?
Is your feature request related to a problem?
As a developer, I want to be able to debug the latency each feature adds to a query during feature logging.
This would help identify features which have an outsized impact on latency.
What solution would you like?
Note - the queries below are taken from a POC repo I created here.
Add a field similar to
"time_in_nanos"
to the feature logs in the SLTR query response when"profile": true
, e.g.Request
Response:
What alternatives have you considered?
This feature could also be implemented via an SLTR query parameter instead of through the
profile
API setting.Do you have any additional context?
Please let me know if there are alternative ways to debug the latency each feature adds to a query during feature logging already using the plugin, as I couldn't find any references in the official documentation
The text was updated successfully, but these errors were encountered: