-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[receiver/expvarreceiver] Overall structure for new expvarreceiver #9747
Conversation
|
||
## Configuration | ||
|
||
### Default |
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.
Once we know the list of default metrics we are going to export, we should add them here in that PR with an example of how to disable them if you're not interested in gc_pause.time
for example.
Hi @dmitryax would you be able to take a look at this PR? 😃 |
Co-authored-by: Daniel Jaglowski <jaglows3@gmail.com>
RE the changelog checks - I will update it once this PR is approved and ready to be merged. It's the kind of thing that gets a conflict every time I rebase on master because of other things being added to the changelog constantly. |
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.
LGTM, pending a changelog entry
Thanks for the review @djaglowski! - changelog is updated |
Description: This PR is the initial Config and Factory implementations for the expvar receiver. There is no receiver implementation yet, it is just a skeleton and basic test for loading config from yaml.
The
expvarreceiver
intends to collect memstats from Golang applications. The configuration options are collection interval, http client config, and enabling/disabling metrics by name.Link to tracking Issue: #9592
Testing: Basic tests for config validation. More rigorous unit tests will be added when there is more implementation to test.
Documentation: The README details configuration options and defaults. It doesn't yet go into details on the
metrics
section because the list of metrics names from memstats still needs to be defined by the receiver.