{{ message }}
Repository navigation
Custom log format - using port as protocol #2891
Description
My nginx log format is this:
log_format logger-json escape=json '{'
'"remote_addr": "$remote_addr", "remote_user": "$remote_user"'
', "time_iso8601": "$time_iso8601", "msec": $msec'
', "host": "$http_host", "method": "$request_method", "uri": "$request_uri"'
', "status": "$status", "body_bytes_sent": "$body_bytes_sent"'
', "referer": "$http_referer", "user_agent": "$http_user_agent", "server_name": "$server_name"'
', "port": "$server_port", "ut": "$upstream_response_time", "rl": "$request_length"'
', "ssl_client_s_dn": "$ssl_client_s_dn"'
', "ssl_cipher": "$ssl_cipher", "ssl_protocol": "$ssl_protocol"'
', "rt": "$request_time", "uct": "$upstream_connect_time"'
'}';Which I have converted to goaccess configuration as
time-format %H:%M:%S
date-format %Y-%m-%d
log-format {"remote_addr": "%h", "remote_user": "%e", "time_iso8601": "%dT%t+%^", "msec": %^, "host": "%^", "method": "%m", "uri": "%U", "status": "%s", "body_bytes_sent": "%b", "referer": "%R", "user_agent": "%u", "server_name": "%v", "port": "%H", "ut": "%^", "rl": "%^", "ssl_client_s_dn": "%^", "ssl_cipher": "%k", "ssl_protocol": "%K", "rt": "%T", "uct": "%^"}
However, this is not fully accepted:
Token '80' doesn't match specifier '%H'
Would it be possible to allow %H to accept 80 for HTTP and 443 for HTTPS ?
--
And semi-related, I'm surprised there seems to be no specifier for request_length, but that might warrant its own ticket
Activity
allinurl commentedon Oct 26, 2025
Would you be able to post a few sample lines from your log so I can take a look?
%His for the actual protocol so it won't accept the port.ds-cbo commentedon Oct 28, 2025
Sure:
I thought the protocol would be HTTP/HTTPS, maybe the naming is a bit confusing then
ds-cbo commentedon Oct 28, 2025
whoops, wrong button, could you re-open?
allinurl commentedon Oct 29, 2025
Good point. HTTP/HTTPS refers to the protocol (secure or not), while HTTP/1.0, 1.1, 2, and 3 are versions of that protocol. We could add an option to accept that instead? or if you don't need to link the request to the protocol directly, you could use
%efor the port to reuse the user panel.ds-cbo commentedon Oct 30, 2025
I am already using %e for remote_user, but I could use %M instead of for mime-type, it's a bit wonky but will do for now. Thanks