-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 ~200 more Couchbase metrics via Buckets endpoint #9032
Conversation
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.
🤝 ✅ CLA has been signed. Thank you!
I think we may want to consider adding |
Done |
2623078
to
a8c1c91
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.
Looks like new artifacts were built from this PR. Get them here!
Artifact URLs
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.
Looks good to me
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.
Looks like new artifacts were built from this PR. Get them here!
Artifact URLs
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.
this is probably fine, but I was thinking we needed fields_excluded, but maybe not?
I guess my thinking was that if the user is handpicking every field they do want, they won't have much of a need for fields excluded? |
It depends. if you want all fields except 1 or 2, but you also want to get any fields added from plugin updates, exclude would be a better fit. I'm not certain it matters that much for this, but that's the idea. |
* Couchbase new metrics for buckets * updated * update to simplify two different modes. * cleanup code * linter telling me to fix things I didn't do * add include/exclude filter * update sample config * appease the linter * Update README.md * make all metrics configurable, defaults as just 'basic bucket metrics' * check error in test
The additional metrics are configurable as
detailed
metrics.Many of the stats being added correlate directly to graphs available on the Couchbase UI, you can hover them to see their metric 'name'.
Every gather of the
detailed
metrics will gather the latest Couchbase metrics (from the last possible second).resolves #4152