Is your feature request related to a problem? Please describe.
It's very frustrating to try and determine which log file is for which site since they are all named after the arbitrary ID that they are assigned when created.
Describe the solution you'd like
It would be nice to instead have them named after the first domain in the domain_names list.
~BEFORE~
# ls
proxy_host-1.log proxy_host-10.log proxy_host-11.log proxy_host-2.log proxy_host-3.log proxy_host-4.log proxy_host-5.log proxy_host-6.log proxy_host-7.log proxy_host-8.log proxy_host-9.log
~AFTER~
# ls
domain.example.com.log fqdn.something.log ...
Using the template on how the domain names are set for server_name, I assume this can be accomplished by simply changing the access log line to something like this (proxy host as the example):
access_log /data/logs/{{ domain_names[0] }}.log proxy;
OR
access_log /data/logs/{{ domain_names | first }}.log proxy;
Describe alternatives you've considered
I tried to just add a custom access_log line to the advanced configuration, but instead of overwriting the previous setting it sends logs to both files.
Additional context
N/A
Is your feature request related to a problem? Please describe.
It's very frustrating to try and determine which log file is for which site since they are all named after the arbitrary ID that they are assigned when created.
Describe the solution you'd like
It would be nice to instead have them named after the first domain in the
domain_nameslist.Using the template on how the domain names are set for
server_name, I assume this can be accomplished by simply changing the access log line to something like this (proxy host as the example):Describe alternatives you've considered
I tried to just add a custom
access_logline to the advanced configuration, but instead of overwriting the previous setting it sends logs to both files.Additional context
N/A