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

logdna-agent not bug in -f and not respecting filelist #224

Open
amit777 opened this issue Apr 1, 2021 · 1 comment
Open

logdna-agent not bug in -f and not respecting filelist #224

amit777 opened this issue Apr 1, 2021 · 1 comment

Comments

@amit777
Copy link

amit777 commented Apr 1, 2021

There seems to be 2 bugs.. Not sure if they are related:

  1. logdna-agent -f /var/log/messages seems to not just monitor the single file, but rather all my logs within /var/log. It generates the following /etc/logdna.conf
logdir   =  /var/log, /var/log/messages

So it doesn't seem to set the right key, to logfile = [...]. It also is adding the top level /var/log folder which has a lot of log files in it.

I've tried to manually edit /etc/logdna.conf and restart the service, but no matter what I do, it seems to still pickup all the files.. ive tried the following:

logdir   = /var/log/messages
logfile   =  /var/log/messages
@amit777
Copy link
Author

amit777 commented Apr 2, 2021

I was able to figure out a workaround by playing with the source here.

logdir = /var/log/secure,/var/log/maillog,/var/log/haproxy.log,/var/log/redis.log,/var/log/cron,/var/log/yum.log,/var/log/fail2ban.log,/var/log/messages,/var/log/dnf*.log,/var/log/redis-local.log,/var/log/mongodb/mongo*.log,/var/log/audit/audit.log"

This seems to do that trick. The cli tool seems to stuff in /var/messages for some reason so I'm avoiding using that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant