-
Notifications
You must be signed in to change notification settings - Fork 814
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
[mongo] add tcmalloc metrics #1979
Conversation
[[email protected]] rebased on #1979 → `collect_wiredtiger_metrics` option.
b0fc02d
to
8863ba8
Compare
[[email protected]] rebased on #1979 → `collect_wiredtiger_metrics` option.
"uptime": GAUGE, | ||
} | ||
|
||
V2_ONLY_METRICS = { |
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 don't think this is the entire list of metrics available only in mongo 2.x. E.g. I don't think that Mongo 3.x will return "cursors.totalOpen" or "cursors.timedOut"
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 just ran some tests against a MongoDB 2.6 and 3.0 instances, the V2_ONLY_METRICS
seens exhaustive.
cursors.totalOpen
or cursors.timedOut
are still part of MongoDB 3.0 as stated in the MongoDB 3.0 documentation
[[email protected]] rebased to sync with MongoDB last changes
Split the metric list in multiple parts: * `COMMON_METRICS`: default metrics to collect * `V2_ONLY_METRICS`: metrics available in MongoDB 2.x only * `TCMALLOC_METRICS`: TCMalloc memory allocator metrics It's easier to assess the check coverage in our CI, and gives more control on the level of metric collection. Create a `collect_tcmalloc_metrics` option (default to False). Extends #1832, thanks a lot @benmccann !
8863ba8
to
ba8760e
Compare
Thanks for your feedback @benmccann. I adressed your comments and rebased the PR. It's ready to be merged now 🚢 |
[[email protected]] rebased on #1979 → `collect_wiredtiger_metrics` option.
[[email protected]] rebased on #1979 → `collect_wiredtiger_metrics` option.
[[email protected]] rebased on #1979 → `wiredtiger` option.
[[email protected]] rebased on #1979 → `wiredtiger` option.
[[email protected]] rebased on #1979 **Additional changes:** * Add the corresponding `wiredtiger` option in `additional_metrics` * More friendly WiredTiger metric aliases * Switch some WiredTiger metric types from `gauge` to `rate`
[[email protected]] rebased on #1979 **Additional changes:** * Add the corresponding `wiredtiger` option in `additional_metrics` * More friendly WiredTiger metric aliases * Switch some WiredTiger metric types from `gauge` to `rate`
[[email protected]] rebased on #1979 **Additional changes:** * Add the corresponding `wiredtiger` option in `additional_metrics` * More friendly WiredTiger metric aliases * Switch some WiredTiger metric types from `gauge` to `rate`
[[email protected]] rebased on #1979 **Additional changes:** * Add the corresponding `wiredtiger` option in `additional_metrics` * More friendly WiredTiger metric aliases * Switch some WiredTiger metric types from `gauge` to `rate`
Rebased of #1832 on master, thanks a lot @benmccann !
My two cents:
Split the metric list in multiple parts:
COMMON_METRICS
: default metrics to collectV2_ONLY_METRICS
: metrics available in MongoDB 2.x onlyTCMALLOC_METRICS
: TCMalloc memory allocator metricsIt's easier to assess the check coverage in our CI, and gives more
control on the level of metric collection.
Create a
collect_tcmalloc_metrics
option (default to False).