Skip to content
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

Set default metricsets for modules #6668

Closed
32 tasks done
ruflin opened this issue Mar 26, 2018 · 8 comments
Closed
32 tasks done

Set default metricsets for modules #6668

ruflin opened this issue Mar 26, 2018 · 8 comments
Assignees

Comments

@ruflin
Copy link
Member

ruflin commented Mar 26, 2018

Recently the feature to set default metricsets for a module were introduced. If a module is enabled an no metricsets are set, this list of metricsets is used. Now for each module the metricsets must be defined. In general this is all metricsets which are GA but there might be some exceptions like prometheus where the default one is only collector.

This issue is to track the progress on setting the defaults metricsets for all modules.

@ruflin
Copy link
Member Author

ruflin commented Mar 27, 2018

@jsoriano I started working from the top of the list.

@ruflin
Copy link
Member Author

ruflin commented Mar 27, 2018

@jsoriano When changing each module I also directly check #6672 So I add enabled: true to the reference config file (if there is one) and remove enabled: * from the short config.

Other changes I do:

  • Add a note to the docs
  • Add an entry to the changelog

@jsoriano
Copy link
Member

I start from the bottom then :)

@ruflin
Copy link
Member Author

ruflin commented Apr 3, 2018

All changelog entries which have to be added later. Lets use this comment to collect them.

- Set all metricsets as default metricsets in Ceph module. {pull}6676[6676]
- Set `container`, `cpu`, `diskio`, `healthcheck`, `info`, `memory` and `network` in docker module as default. {pull}6718[6718]
- Set `cpu`, `load`, `memory`, `network`, `process` and `process_summary` as default metricsets in system module. {pull}6689[6689]
- Set `collector` as default metricset in Dropwizard module. {pull}6669[6669]
- Set `info` and `keyspace` as default metricsets in redis module. {pull}6742[6742]
- Set `connection` as default metricset in rabbitmq module. {pull}6743[6743]
- Set all metricsets as default metricsets in Elasticsearch module. {pull}6755[6755]
- Set all metricsets as default metricsets in Etcd module. {pull}6756[6756]
- Set server metricsets as default in Graphite module. {pull}6757[6757]
- Set all metricsets as default metricsets in HAProxy module. {pull}6758[6758]
- Set all metricsets as default metricsets in Kafka module. {pull}6759[6759]
- Set all metricsets as default metricsets in postgresql module. {pull}6761[6761]
- Set status metricsets as default in Kibana module. {pull}6762[6762]
- Set all metricsets as default metricsets in Logstash module. {pull}6763[6763]
- Set `container`, `node`, `pod`, `system`, `volume` as default in Kubernetes module. {pull} 6764[6764]
- Set `stats` as default in memcached module. {pull}6765[6765]
- Set all metricsets as default metricsets in Mongodb module. {pull}6766[6766]
- Set `pool` as default metricset for php_fpm module. {pull}6768[6768]
- Set `status` as default metricset for mysql module. {pull} 6769[6769]
- Set `stubstatus` as default metricset for nginx module. {pull}6770[6770]

@ruflin
Copy link
Member Author

ruflin commented Apr 4, 2018

I left the golang module untouched as it's still experimental and I think in this stage we should not have defaults.

@ruflin
Copy link
Member Author

ruflin commented Apr 4, 2018

I checked off http and suggest not to add any defaults. For the json metricset it is always required to set a correct path as / is probably not the one that is expected. And for the server one not sure if the expectation of enabling the http module would be that a port is opened.

@ruflin
Copy link
Member Author

ruflin commented Apr 4, 2018

Similar thing to the above applies for Jolokia and I also checked it off. The jmx metricset always requires manual configuration so it does not make much sense to have it as a default.

@ruflin
Copy link
Member Author

ruflin commented Apr 5, 2018

Closing as all changes have been merged and changelog PR is open here #6781

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants