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 have two questions to ask: goaccess version 1.7.2 analysis nginx log
First, why is there no AVG .T.S 、CUM. T.S、MAX. T.S in the indicators I count. What should I do to display these three columns and to show them on each statistics panel? this is mine like this :
Second, will GoAccess support statistics on other metrics in the future? For example, "View the last 1,000 records and the most visited pages", "List pages with a transmission time of more than 3 seconds, display the first 20", "List pages with a page request time of more than 3 seconds, and count the number of their occurrences, display the top 100" or whether to support the statistics of custom indicators in the future.
The above questions help me answer them, thank you.
Great questions! to obtain the average, cumulative, and maximum time served using GoAccess, you must enable the logging of response times in your web server. For Nginx, you can include $request_time in your log format, while in Apache, you can use %D and then enable it in your goaccess' log-format.
Yes, #117 should address your second question. This is currently in progress, so please stay tuned for updates.
Hello, I have two questions to ask: goaccess version 1.7.2 analysis nginx log
First, why is there no AVG .T.S 、CUM. T.S、MAX. T.S in the indicators I count. What should I do to display these three columns and to show them on each statistics panel? this is mine like this :
Second, will GoAccess support statistics on other metrics in the future? For example, "View the last 1,000 records and the most visited pages", "List pages with a transmission time of more than 3 seconds, display the first 20", "List pages with a page request time of more than 3 seconds, and count the number of their occurrences, display the top 100" or whether to support the statistics of custom indicators in the future.
The above questions help me answer them, thank you.
@allinurl thanks!
The text was updated successfully, but these errors were encountered: