-
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 WiredTiger metrics #1980
Conversation
0433c67
to
7e7011a
Compare
"tcmalloc.tcmalloc.transfer_cache_free_bytes": GAUGE, | ||
} | ||
|
||
WIREDTIGER_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.
not sure about these metric names...
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 metric names were created by MongoDB. We're simply collecting the metrics that they export. I think it'd be really confusing to remap them to new names because then for every metric we have to go back and figure out what the MongoDB name was to really understand what it's doing.
@yannmh let's talk about the metric names. Everything else is 👍 |
7e7011a
to
33b328c
Compare
By default, the check collects a sample of metrics from MongoDB. The (optional) `additional_metrics` parameter instructs the check to collect additional metrics on specific topics. Available options are: * `durability` - Journaling-related operations and performance * `locks` - Locks * `metrics.commands` - Use of database commands * `tcmalloc` - TCMalloc memory allocator
[[email protected]] rebased on #1979 → `collect_wiredtiger_metrics` option.
33b328c
to
78a6c92
Compare
Closing in favor of #2020 |
Rebase of #1825 on #1979, to collect WiredTiger metrics behind a
additional_metrics
option.Thanks again @benmccann !