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
Is your feature request related to a problem? Please describe.
My nginx issues many logfiles, one per domain name, in the following simplified hierearchy:
/var/log/nginx/client1/${domain_name}_access.log
Where domain_name has many values and changes regularly (we have a dynamic inventory of domain names and the configuration is added automatically in nginx).
I have to manually add all files to the files = [ x, y, z ] for each of my clients, eg:
namespaces:
- name: client&format: '$remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_response_time $upstream_connect_time'source:
files:
- /var/log/nginx/client1/(.*)_access.log # automatically picks up all files matching this pattern at boot and on SIGHUP
Describe alternatives you've considered
I could spin up some kind of patching to the current configuration so that when an new nginx configuration (and logfile) is added, I can add it to the corresponding namespace, but I am not quite sure how much effort it would entice, rather than implement a basic globing in nginxlog-exporter for that feature.
We run bare-metal, not kubernetes. In a K8S environment, I'd have considered adding CRDs maybe to symbolize a namespace and dynamically poplate the configuration with that.
Additional context
The text was updated successfully, but these errors were encountered:
There has not been any activity to this issue in the last 30 days. It will automatically be closed after 7 more days. Remove the stale label to prevent this.
Is your feature request related to a problem? Please describe.
My nginx issues many logfiles, one per domain name, in the following simplified hierearchy:
/var/log/nginx/client1/${domain_name}_access.log
Where
domain_name
has many values and changes regularly (we have a dynamic inventory of domain names and the configuration is added automatically in nginx).I have to manually add all files to the
files = [ x, y, z ]
for each of my clients, eg:Describe the solution you'd like
I'd like the files to be "globable" like this:
Describe alternatives you've considered
I could spin up some kind of patching to the current configuration so that when an new nginx configuration (and logfile) is added, I can add it to the corresponding namespace, but I am not quite sure how much effort it would entice, rather than implement a basic globing in nginxlog-exporter for that feature.
We run bare-metal, not kubernetes. In a K8S environment, I'd have considered adding CRDs maybe to symbolize a namespace and dynamically poplate the configuration with that.
Additional context
The text was updated successfully, but these errors were encountered: