-
Notifications
You must be signed in to change notification settings - Fork 706
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
WIP: Implement mssql base counters #463
WIP: Implement mssql base counters #463
Conversation
8beba59
to
9d481c2
Compare
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.
Thanks for taking this on @secustor! Some naming changes I'd like to see, otherwise looking good
collector/mssql.go
Outdated
@@ -662,6 +666,12 @@ func NewMSSQLCollector() (Collector, error) { | |||
[]string{"instance"}, | |||
nil, | |||
), | |||
AccessMethodsWorktablesFromCacheRatio_Base: prometheus.NewDesc( | |||
prometheus.BuildFQName(Namespace, subsystem, "accessmethods_worktables_from_cache_ratio_lookups"), |
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.
Skip the _ratio
here, since it is not lookups on the ratio
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.
Also, the metric accessmethods_worktables_from_cache_ratio
should probably be accessmethods_worktables_from_cache_hits
, right?
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.
(The above seems to repeat for all the new changes)
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.
The bases have no meaning on itself if you go by the Microsoft documentation.
Better said MS is not sharing what they are in their documentation.
Because of this I would prefer the naming style of @sqlkabouter .
We can't be sure here as we have to go with the documentation of Microsoft.
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 sorry to be a bit contrarian here, but while I appreciate that the documentation is a bit vague and the current naming wrong, I'm not sure I'm keen on merging something which introduces more unclarity. The name here is pretty bad in that regard, in my opinion.
Looking at the docs you linked:
The ratio is the total number of cache hits divided by the total number of cache lookups over the last few thousand page accesses.
By that definition, it seems pretty clear to me that we get the total lookups in the base, and total hits in the "non-base" counter? Are there other reasonable interpretations I'm missing?
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.
It seems to be the case after testing with MS monitoring tools.
Our DB team will hopefully confirm with this Snapshot that the results using Prometheus+WMI_Exporter and MS tools report the same stats.
@carlpett Can give me feedback what is not working in the pipeline? |
@secustor It seems it didn't even try to build... And Github's usability team could do better here I think - I need to hover over the failing check to get the text "AppVeyor was unable to build non-mergeable pull request". So if you resolve the conflict it will build. |
eed771c
to
b2f521d
Compare
I hope you can see the build logs this time? If not, the failing part is linting, specifically that the files are not |
9d1b34e
to
696c447
Compare
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.
Shaping up nicely! Looks like there was a bit too much replaced, so the underlying WMI counters got renamed as well. But after that this looks good to me!
696c447
to
6dad58f
Compare
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.
🎉
Thank you so very much @secustor! 👏 |
…ssql-base-counters WIP: Implement mssql base counters
Resolves #250
Continuation of #352 as this contribution seems to be abandoned.