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
hello,
I think everyone's problems are basically due to the log-format format problem, which makes it impossible to analyze. It would be great if you could provide a way to automatically identify the log-format by reading the first 10 lines of logs or upload a conf file to output the log-format!
At present, the second tool seems to be available, but it only supports nginx, for example, apache does not support it. Reference: https://github.com/stockrt/nginx2goaccess
Thank you so much!
The text was updated successfully, but these errors were encountered:
This sounds fantastic! Do you have any ideas or insights you can share on how this should function for the various log formats available? I'd love to hear them! Thanks
In my (not so humble) opinion it is almost impossible. Why?
If a number 100 appears, which field would it be?
Bytes sent, Response time?
What if it's 300?
HTTP Return Code?
It would only be possible for usual fields, basically text, such as UserAgent, URI, Cookie, etc.
Maybe OK... if you test into all LOGS type formats that GOACCESS support...
hello,
I think everyone's problems are basically due to the log-format format problem, which makes it impossible to analyze. It would be great if you could provide a way to automatically identify the log-format by reading the first 10 lines of logs or upload a conf file to output the log-format!
At present, the second tool seems to be available, but it only supports nginx, for example, apache does not support it. Reference: https://github.com/stockrt/nginx2goaccess
Thank you so much!
The text was updated successfully, but these errors were encountered: