Hello,
I'm not sure what you'd like to achieve. `nxlog.conf` is the main config file, where you define sources of your logs, the way of handling them, and targets where logs should be forwarded.
I recommend spending a while on analyzing the documentation (I assume you're interested in the community edition): https://nxlog.co/docs/nxlog-ce/nxlog-reference-manual.html. You can find many examples of configs there - I believe that's the best starting point.
Once you find what's interesting for you - solving any issues would much more feasible.
Best of luck!
Rafal
Comments (3)
I want nxlog to log, when it parses the config file. I want it to log, that it found the correct include file. This is helpful when you include with wildcards.
Sure,
nxlog
is a perfect solution when it comes to logging!However, we'd need to know what kind of logs and from which sources you want to collect, as well as what would be the expected destination.
Especially in terms of wildcards, it would be good to know which operating system do you use?
Could you share your
conf
files and tell more about the context of your log collection?Regards,
Rafal
nxlog.conf:
path/additional/route1.conf:
I have no way of knowing if route1is loaded if nothing is logged per tcp. I want nxlog to print into its internal log (not the om_file), that it successfully included route1.conf.