It would seem that managing a few hundred computers nxlog conf files would get
difficult. The problem doesn't scale well, especially on Windows. I propose
allowing nxlog to use the INI format on Windows machines. This would allow
centralized management via active directory group policy preferences.
90% of the configuration declarations would work OOB, for example:
<Processor buffer_udp>
Module pm_buffer
## 1Mb buffer
MaxSize 512
Type Mem
## Warn at 512k
WarnLimit 256
</Processor>
Would look like:
[Processor::buffer_udp]
Module=pm_buffer
;## 1Mb buffer
MaxSize=512
Type=Mem
;## Warn at 512k
WarnLimit=256
This ugly to look at but it can be fully managed by group policy preferences.
The only difficulties I see would be with EXEC blocks. Typically INI files
don't have multi-line entries and group policy preferences doesn't write them
however I think it can be worked around, primarily because EXEC blocks aren't
supposed to be multi-line, hence all the '\' escaping.
With the rather uncreative use of multiple EXEC statements (e.g. EXEC1, EXEC2,
EXEC3) I think feature parity can be achieved. Again, it would look ugly, but
it would be manageable.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
