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

path variable support and new log file detection #481

Open
jiejisheng opened this issue Jul 2, 2015 · 4 comments
Open

path variable support and new log file detection #481

jiejisheng opened this issue Jul 2, 2015 · 4 comments

Comments

@jiejisheng
Copy link

[Backgroud:]

The nginx log files located at .../%{YEAR}/%{MONTH}, and the a new log file would be created with name %{YY.MM.DD}-access.log everyday.

[Requirement:]

  1. Variable Support in path
  2. With globs or path, new file detections would be nice instead of restarting the service
@lmorfitt
Copy link

lmorfitt commented Jul 3, 2015

@jiejisheng have you tried the path formatting of /var/logs/nginx///*.log ?

@jiejisheng
Copy link
Author

@lmorfitt , Yup, the issue is that this log directory won't be cleaned up, so this folder contains logs of year 2013 or even earlier. To avoid the unnecessary file monitor, the accurate path/file naming format would reduce the cost.

@lmorfitt
Copy link

lmorfitt commented Jul 3, 2015

@jiejisheng Are, I see. Personally I would logrotate (with compress) the older files after 30 days (or something sane), thus LSF will not monitor .gz files

@angel-smile
Copy link

I have got the same problem with log-courier. So this hasn't been resolved in logstash-forwarder either?

@jiejisheng Can I know what's your workaround at the moment?

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

5 participants