Metrics that help measure connection saturation and roundtrip latency #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Includes four new metrics:
beanstalk_client_command_roundtrip_latency
to measure the time between the command being sent and the response arriving to the client.beanstalk_client_command_count
to measure the number of commands sent to beanstalkd.beanstalk_client_command_error_count
to measure the number of errors returned from the commands sent to beanstalkd.beanstalk_client_command_queue_latency
to measure the time between acquiring the lock to execute commands.Those metrics were added via opencensus and can views that bound to them can be accessed via the
beanstalk.MetricViews
method instats.go
Example: