The exception handling in Nathean Analytics is a implementation of the Logging Application Block In Microsoft Enterprise Library.

The block can route log entries to a Windows Event Log, a database, or a text (or XML) file. It can also generate an email message containing the logging information, a message you can route through Windows Message Queuing (using a distributor service provided with the block). And, if none of these built-in capabilities meets your requirements, you can create a provider that sends the log entry to any other custom location or executes some other action.
In your application, you simply generate a log entry using a suitable logging object, such as the LogWriter class, and then call a method to write the information it contains to the logging system. The Logging block routes the log message through any filters you define in your configuration, and on to the listeners that you configure. Each listener defines the target of the log entry, such as Windows Event Log or an email message, and uses a formatter to generate suitably formatted content for that logging target.

When you enable application diagnostics, you also choose the Level. The following table shows the categories of logs each level includes:

Level Included log categories
Disabled None
Error Error, Critical
Warning Warning, Error, Critical
Information Info, Warning, Error, Critical
Verbose Trace, Debug, Info, Warning, Error, Critical (all categories)

The listeners are configured and switched on in the section of the web.config and Nathean Schedule Service.exe.config files. The files are preconfigured with the following configurations but these configurations can be easily modified.

Event Log Listener When enabled, this listener writes error messages to the Event Viewer on the server.

Flat File Trace Listener When enabled, this listener writes all messages to the file ..\logs\trace.log – this version is never truncated and so much be manually done.

Error File Trace Listener When enabled, this listener writes error messages to the file ..\logs\error.log – this version is never truncated and so much be manually done.

Info File Trace Listener When enabled, this listener writes information messages to the file ..\logs\info.log – this version is never truncated and so much be manually done.

Rolling Flat File Trace Listener When enabled, this listener writes all messages to the file ..\logs\trace_xxxx.log – this version limits each trace*.log file to 10mb and keeps the last 10 files is is truncated and so there is no need to manually do this.

There is a performance penalty for using them, therefore it is recommended is stable production environments to use

Error File Trace Listener and Event Log Listener

In environments for development and testing or production environments in which there are reported issues, use

Error File Trace Listener and Rolling Flat File Trace Listener

You can configure your own which suits your own needs, for example you can create a listener which emails critical errors to IT support eg when a data connector is failing to connect to the server.

The logs generated are large so we recommend using the following log reader utility, Glogg or something similar.

Revision: 2
Last modified: May 16, 2019

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment