-
Notifications
You must be signed in to change notification settings - Fork 558
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
Add metrics to SwimMembershipProtocol #6003
Comments
I could add a separate section to the dashboard for swim using these metrics |
Since we are broadcasting the gossip of these updates with no answers, how could we go about measuring this gossip latency? |
Honestly, it sounds to me like distributed tracing would be the tool we want to have here. Start an operation somewhere, measure when it completes somewhere else, possibly with hops. As we don't have that yet, I would postpone this. However, there may be other metrics we'd like just from the local node? |
The other thing we could measure perhaps is sync() we have a response for this one. |
We could also try to just export the current state as metrics. Then we could derive additional properties such as "how long does it take to propagate changes throughout the entire cluster" by calculating it on the metrics. Not ideal but I feel like just exporting the current state of SWIM as metrics is useful already. |
@oleschoenburg If I understood correctly we would export the local state of all members on each node? |
Description
To help tune the config parameters of Swim protocol, it would be useful to add some metrics.
Examples:
Related to #4827 (comment) #4827 (comment)
The text was updated successfully, but these errors were encountered: