-
Notifications
You must be signed in to change notification settings - Fork 15
Remove local vs remote host selected metric #4922
Conversation
Generate changelog in
|
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.
🚀
…db into remove-local-host-metrics
@@ -93,10 +87,6 @@ public CassandraService( | |||
Blacklist blacklist, | |||
CassandraClientPoolMetrics poolMetrics) { | |||
this.metricsManager = metricsManager; |
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.
I'm wondering if instead you could do @jeremyk-91 's filtering? So filter when this is 1, but publish when it's not?
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.
I'm removing it more because I don't think I have ever used it after the initial rollout. So even if we filter it, would it be used in debugging?
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.
I've seen it go down and slowly recover before. But I think you might be right, there might not be any in keeping the complexity here
Goals (and why):
Our internal fleet has long since moved to using the local weighting of 1.0, so this metric generally just shows a straight line all of the time.
Implementation Description (bullets):
Removed counters recording when local or remote host was selected.
Testing (What was existing testing like? What have you done to improve it?):
N/A.
Concerns (what feedback would you like?):
Does anyone actually look at this metric, and/or is it ever useful?
Where should we start reviewing?:
CassandraService
Priority (whenever / two weeks / yesterday):
Whenever