Log files with wildcards stopped being ingested after upgrading to 1.6.1

After upgrading the logdna-agent from 1.5.6 to version 1.6.1 (running on Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-1048-aws x86_64)), LogDNA stopped receiving logs from our systems. Here’s an analysis from the terminal:

ubuntu@ip-172-31-57-147:/var/log$ cat /etc/logdna.conf 
logdir = /home/apifier/*.log,/var/log/nginx/error.log
key = [REDACTED]

ubuntu@ip-172-31-57-147:/var/log$ sudo systemctl start logdna-agent

ubuntu@ip-172-31-57-147:/var/log$ cat logdna-agent.log
[190918 09:50:34] logdna-agent 1.6.1 started on ip-172-31-57-147 (172.31.57.147)
[190918 09:50:34] Streaming /var/log/nginx/error.log: 1 file(s)

ubuntu@ip-172-31-57-147:/var/log$ ls /home/apifier/*.log
/home/apifier/[e-mail]  /home/apifier/[e-mail]     /home/apifier/newrelic_agent.log
/home/apifier/[e-mail]  /home/apifier/[e-mail]  /home/apifier/system.log
/home/apifier/[e-mail]  /home/apifier/[e-mail]       /home/apifier/[e-mail]

Basically, it seems LogDNA agent is no longer able to handle wildcards in logdir option, such as /home/apifier/*.log. When we update /etc/logdna.conf as follows:

logdir = /home/apifier/[e-mail],/home/apifier/*.log,/var/log/nginx/error.log
key = [REDACTED]

then streaming of the file [e-mail] resumes normally.

[andkon]

@jancurn it was! Mostly it was an ephemeral problem that showed up on your end because we screwed up and pushed 1.6.1 early. I wanted to verify this was for sure fixed in 1.6.2 before closing, and can confirm it does indeed.

[jancurn]

Please, can you add some integration test for this, so that it doesn’t happen again?