-
Notifications
You must be signed in to change notification settings - Fork 18
Add tracing spans for pipeline and transaction functions #284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Adam Fowler <adamfowler71@gmail.com>
|
✅ Pull request has performance improvements ✅ Summary
New baseline 'pull_request' is BETTER than the 'main' baseline thresholds. Full Benchmark ComparisonComparing results between 'main' and 'pull_request'ValkeyBenchmarksClient: GET benchmark metricsMalloc (total): results within specified thresholds, fold down for details.
Client: GET benchmark | parallel 20 | 20 concurrent connections metricsMalloc (total): results within specified thresholds, fold down for details.
Connection: GET benchmark metricsMalloc (total): results within specified thresholds, fold down for details.
Connection: GET benchmark – NoOpTracer metricsMalloc (total): results within specified thresholds, fold down for details.
Connection: Pipeline array benchmark metricsMalloc (total): results within specified thresholds, fold down for details.
Connection: Pipeline benchmark metricsMalloc (total): results within specified thresholds, fold down for details.
HashSlot – {user}.whatever metricsMalloc (total): results within specified thresholds, fold down for details.
ValkeyCommandEncoder – Command with 7 words metricsMalloc (total): results within specified thresholds, fold down for details.
ValkeyCommandEncoder – Simple GET metricsMalloc (total): results within specified thresholds, fold down for details.
ValkeyCommandEncoder – Simple MGET 15 keys metricsMalloc (total): results within specified thresholds, fold down for details.
|
| span?.updateAttributes { attributes in | ||
| self.applyCommonAttributes(to: &attributes, commandName: Command.name) | ||
| self.applyCommonAttributes(to: &attributes) | ||
| attributes[self.configuration.tracing.attributeNames.databaseOperationName] = Command.name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also add databaseNumber here as well for better tracing ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's not an obvious Otel parameter to use for database number. See https://opentelemetry.io/docs/specs/semconv/registry/attributes/db/
nilanshu-sharma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added comments.
Signed-off-by: Adam Fowler <adamfowler71@gmail.com>
nilanshu-sharma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
This add tracing spans for the pipeline and transaction functions. Span name is either
PipelineorMULTI. The database operation name though is a list of the commands concatenated together egSET,SET,INCR.None of the functions report errors for individual commands as the Results returned by the commands are not processed and processing them would add additional The pipeline functions don't report errors as it doesn't process errors it only returns a collection of Results. The transaction functions report errors returned by
EXECbut again errors from individual commands are not reported.@slashmo