You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
In the documentation for the logentires agent, there is a section about using wildcards for a log file's path in order to match multiple files: https://logentries.com/doc/agent/#following
Among the values in my node[:logentries][:log_files] attribute is the mapping 'Postgres' => '/var/log/postgres/postgres-*.log'. I discovered that this result in logentries following that as a literal pathname. When I ran the same command manually from the shell, it correctly registered the path of the real matching file, /var/log/postgres/postgres-9.3-main.log. Perhaps something in this cookbook is suppressing the shell expansion.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the documentation for the logentires agent, there is a section about using wildcards for a log file's path in order to match multiple files: https://logentries.com/doc/agent/#following
Among the values in my
node[:logentries][:log_files]
attribute is the mapping'Postgres' => '/var/log/postgres/postgres-*.log'
. I discovered that this result in logentries following that as a literal pathname. When I ran the same command manually from the shell, it correctly registered the path of the real matching file,/var/log/postgres/postgres-9.3-main.log
. Perhaps something in this cookbook is suppressing the shell expansion.The text was updated successfully, but these errors were encountered: