-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
How to parse multiple log sources using log-file config option? #734
Comments
Actually this should work. v1.2 did in fact implement the ability to parse multiple source. However, you will need to feed an actual access log to |
"The expansion such as access.log*" what do you mean ? |
That's right. The shell expands the |
if I understood, you mean that |
Using
|
my bad, my english level need some improvment :) can we tell goaccess to self define the log format for each files ? |
No worries :) What do you mean with self define the log-format? #587 will address this if it's what you are asking. |
Interesting issue. Actually what I mean is to let goaccess define by itself which log format it need to process. I am new to log management so I might say s**t however I m thinking. If you got log files which contains COMBINED, VCOMBINED, COMMON, VCOMMON & W3C formats in your data dir, goaccess will identified them and process them accordingly to their own format. Is that possible ? access.log and error.log from apache2.4 doesn t have the same format error: access: other_vhosts_access: I m asking this because a ELK stack might have this ability however goaccess is a much lighter and easy to use log analyzer. |
I see, currently it doesn't have the ability to parse multiple log formats. #213 will address this. |
Closing this. #213 will address different log formats. |
Hi guys,
Is there anyway to provide multiple log sources to goaccess with a log-file parameter which could looks like :
log-file /var/log/*/*/*.log
?the idea behind is to build a common directory to all my logs from host and container within 1 directory like
/my/var/log
in this directory I coul bind volumes like that
docker run -v /my/var/log/myapp/var/log:/var/log [...]
docker run -v /my/var/log/myotherapp/var/log:/var/log [...]
docker run -v /my/var/log/anapp/var/log:/var/log [...]
+
mkdir -p /my/var/log/host/var/log
+ configure app to redirect logs to that specific dirOnce I have done that, I can bind /my/var/log/ to goaccess container, define log-file /var/log///*.log and the process will take care of parsing all logs, define the proper log-format and generate report(s)
I m not sure it meant to be like that, but that will be so awesome
What do you think ?
The text was updated successfully, but these errors were encountered: