-
Notifications
You must be signed in to change notification settings - Fork 107
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
It would be great if there were more example log-courier configurations. #26
Comments
Hi @shurane I did once have a configuration file outlining all the various options in use but it became a bit cumbersome as it grew. Instead I decided to do a small collection here: Is this what you had in mind? If you have any examples of your own or requests for examples I can add to that list. Thanks Jason |
I must be blind, I didn't notice that. Thanks @driskell. It might be worth mentioning if |
The list of examples doesn't show the use of the "general" section. How to enable administration and change the default admin listen address for example. |
The link is now a 404 |
Whoops. Yes it is. See here for the files: I'll create issue to update docs |
To check, all examples are yaml now? There are no longer any json examples? |
I've fixed the 404 and was meant to add a new JSON example but didn't commit it 😩 I'll push up the JSON example tonight or tomorrow. There's an in-page example though in the configuration docs where I try to describe the config formats. Hope it helps. |
Added a JSON example now. I'll get some more detailed ones added in the future with everything in them and lots of comments. |
https://github.com/driskell/log-courier/blob/develop/docs/Configuration.md is awesome documentation, but I would love to see some example configurations, much in the line of all the examples for @coolacid's https://github.com/coolacid/GettingStartedWithELK repo.
It's probably worth mentioning if
log-courier
is backwards compatible withlogstash-forwarder
configs as well.I'm drawing inspiration for a well detailed config mainly from this ansible playbook.yml and this elasticsearch.yml.
The text was updated successfully, but these errors were encountered: