Hi all,
I've been trying to use nxlog in conjunction with an ELK setup.
We have an IIS "cluster" (as in not Windows cluster, but several load
balanced IIS instances), serving a number of sites. As the logs accumulate
(1 file/hour), and there's usually no need to remove old logs, the files
just accumulate there.
I tried monitoring two of the IIS log folders (see nxlog config here:
https://gist.github.com/smarmie/58b213e9f336773c6b4c ), each having ~8k
files, and the nxlog.exe process eats ~520MB RAM already at startup.
Do you think this is a normal behavior? The configcache.dat file that
tracks all these is only 1.25MB.
Thanks.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
