Skip to content
This repository has been archived by the owner on Mar 9, 2024. It is now read-only.

default process_exporter_names #10

Closed
gajowi opened this issue Aug 21, 2019 · 4 comments
Closed

default process_exporter_names #10

gajowi opened this issue Aug 21, 2019 · 4 comments

Comments

@gajowi
Copy link
Collaborator

gajowi commented Aug 21, 2019

For consideration.
While the default variable is empty, there is no config.yml file so no test coverage of that functionality.
We could follow the project documentation and set a non-empty default

The default config shipped with the deb/rpm packages is:

process_names:
  - name: "{{.Comm}}"
    cmdline:
    - '.+'

Or not. I think it is an open design decision and don't mind either way.

In any case, this issue is now noted and is discoverable if related issues come up in future.

An alternative approach is to tweak the CI test env. Perhaps a non-empty default is simpler. Doing nothing is even simpler :-)

@paulfantom
Copy link
Member

Usually we follow both paths at the same time in 2 separate test scenarios. First one is testing default settings without changing any variables and second one tries to change as many as possible. Both scenarios should give a working setup.

I would suggest to start with a default list which is also shipped with deb/rpm packages.

For a reference design in setting up test scenarios you can go to https://github.com/cloudalchemy/ansible-prometheus/tree/master/molecule

@gajowi
Copy link
Collaborator Author

gajowi commented Aug 21, 2019

OK. I'll read more and work up a PR.

@gajowi gajowi mentioned this issue Aug 22, 2019
@gajowi
Copy link
Collaborator Author

gajowi commented Aug 23, 2019

closed by applying #11 - which lists more detail

@gajowi gajowi closed this as completed Aug 23, 2019
@lock
Copy link

lock bot commented Sep 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Sep 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants