Yeah, extending the logging diagnostic would ease my concern entirely
(actually, it would be most preferable), so long as it was complete enough
to answer what/when/where/why

Where would have to include the hostname of the nxlog instance that
experienced the fault, so the log can be traced back properly in a chained
nxlog deployment. It must also include the full raw input, and a good
indication of what caused it to fault.

For the sake of debugging it would be useful to document which function a
breakpoint could be placed on, when doing bug triage.

On Thursday, 21 August 2014, Botond Botyanszki <b...@nxlog.org> wrote:

> Hi,
>
> On Tue, 19 Aug 2014 20:42:37 +1200
> Cameron Kerr <cameron.kerr...@gmail.com <javascript:;>> wrote:
>
> > The configuration tree could be modified to support something like a
> > simple try/catch
> Extending the configuration language with try-catch and other constructs
> would lead to a lot of complexity. It was never intended to be a full
> featured language, i.e. we don't want to reimplement perl or similar. For
> that there is already xm_perl.
> If we'd introduce the configurable error handling, the 'abort evaluation
> and log error' strategy would also achieve what you'd most likely do with
> try/catch while keeping the config a lot simpler.
>
> > Or perhaps it would be better to synthesise a new log message [error
> > report] (that could be forwarded like any other non-debug internal log)
> > that contained a complete diagnostic of the error message. This would
> > make nxlog easier to support as well.
>
> This would make more sense to extend the internal logging infrastructure
> and be able to add more contextual data such as the log that triggered
> the error.
>
> Regards,
> Botond
>


-- 
-- 
Cameron Kerr <cameron.kerr...@gmail.com>
See my blog at http://distracted-it.blogspot.co.nz/  (previously
http://humbledown.org/)
Skype me on cameron.kerr.nz
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users

Reply via email to