Feature Request - allow multiple config files / a folder for config files

Tags:

#1 mats

I would like to propose a possibility to have multiple config files in a folder (like how telegraf works)

"Configuration file locations The location of the configuration file can be set via the --config command line flag. Telegraf will also pick up all files matching the pattern *.conf if the -config-directory command line flag is used.

On most systems, the default locations are /etc/telegraf/telegraf.conf for the main configuration file and /etc/telegraf/telegraf.d for the directory of configuration files."

I belive this would enhance NXlog by making it a lot easier to implement where there is a need for different log sources.

It will allow the owner/maintainer of a function or application to create their own nxlog config for their needs. IE The operating system team manages the config file for the system logs The database team manages the config file for the logging required for example SQL server The web server team manages the logging for IIS/Apache

The benefit over having it in one file and have to edit that file for each change in logging needs are:

  • No risk for disruption of other logging on the same system.
  • adding logging for a new app is as easy as dropping a file into the config dir. Very easy for a deployment tool.
  • Clear responsibility - Our app - our config file. Makes paas/saas scenarios a lot easier
#2 b0ti Nxlog ✓ (Last updated )
#1 mats
I would like to propose a possibility to have multiple config files in a folder (like how telegraf works) "Configuration file locations The location of the configuration file can be set via the --config command line flag. Telegraf will also pick up all files matching the pattern *.conf if the -config-directory command line flag is used. On most systems, the default locations are /etc/telegraf/telegraf.conf for the main configuration file and /etc/telegraf/telegraf.d for the directory of configuration files." I belive this would enhance NXlog by making it a lot easier to implement where there is a need for different log sources. It will allow the owner/maintainer of a function or application to create their own nxlog config for their needs. IE The operating system team manages the config file for the system logs The database team manages the config file for the logging required for example SQL server The web server team manages the logging for IIS/Apache The benefit over having it in one file and have to edit that file for each change in logging needs are: No risk for disruption of other logging on the same system. adding logging for a new app is as easy as dropping a file into the config dir. Very easy for a deployment tool. Clear responsibility - Our app - our config file. Makes paas/saas scenarios a lot easier

This is already supported.