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

[Discussion] Logging define to manage the logging.yml file #54

Closed
electrical opened this issue Oct 8, 2013 · 5 comments
Closed

[Discussion] Logging define to manage the logging.yml file #54

electrical opened this issue Oct 8, 2013 · 5 comments

Comments

@electrical
Copy link
Contributor

Im planning to create a define to manage the logging.yml file.
Any idea's about it are welcome.

@ghost ghost assigned electrical Nov 22, 2013
@drewr
Copy link

drewr commented Jan 16, 2014

👍 Main thing I need though is es.logger.level, which might be better handled in the deb/rpm with an $ES_LOGGER_LEVEL var.

@electrical
Copy link
Contributor Author

Think i'll just let it be a puppet file resource for now.
@spinscale is this ES_LOGGER_LEVEL something we can/want to implement?

@faxm0dem
Copy link

a file resource is nice, a config hash is better for hiera :-)

@apple-corps
Copy link

I'm not sure what's so great about hiera. I have a whole bunch of config options to set for the elasticsearch.yml file. A file template seems like a nice way to go, considering I already have an elasticsearch.yml file. I've looked through quite a bit of documentation. Using a whole crapload of hash rocket symbols is troublesome. Can somebody point out some good examples of how config hashes are much better than using template files for configurations with many many options?

@faxm0dem
Copy link

hiera lets you deeply merge configuration hashes. Say you have multiple ES clusters, and would like common options for all, and specific ones for different clusters. Using a file resource, you would have to duplicate configurations. Duplication is both time consuming and error prone.

@electrical electrical removed their assignment Feb 25, 2016
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

4 participants