-
Notifications
You must be signed in to change notification settings - Fork 159
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
Parse Environment Variables located inside log_files.yml #172
Comments
I think this would typically be handled by config management, like chef, puppet, etc., and would be outside the responsibility of remote_syslog2. That being said, it's possible to pass in a list of log files on the command line as additional arguments, so that env vars would be expanded, like:
|
That makes sense, though would get a bit unwieldy beyond a handful of log files. Johnathan On Mon, Sep 26, 2016 at 12:46 PM Mark Martin <
a, pre, code, a:link, body { word-wrap: break-word !important; } I think this would typically be handled by config management, like chef, puppet, etc., and would be outside the responsibility of remote_syslog2. That being said, it's possible to pass in a list of log files on the command line as additional arguments, so that env vars would be expanded, like: remote_syslog -D -d a.example.com -f local0 "${MYVAR}/path/to/logfile.log" "${MYVAR}/path/to/second.log" — You are receiving this because you authored the thread. Reply to this email directly, |
I took the While parsing of ENV variables in |
Submitting this on behalf of a user. When deploying remote_syslog2 in an automated fashion, it helps to be able to use environment variables to automatically point remote_syslog2 in the right direction toward the log files of the application.
Example
Note: the tags are ERB but we could possibly come up with a standard implementation of this.
The text was updated successfully, but these errors were encountered: