Skip to main content

70-562 Health Monitoring


Programmatic access to trace output from System.Web.TraceContext, using the TraceFinished event.

TraceContextRecord encapsulates a trace message, it can be put in CAtegory, ErrorInfo gets an exception, IsWarning indicates if it's a warning.

One has to attach en avent heandler to the Trace.TraceFinihsed += new TraceContextEventHandler(ONTraceFinished);

This handler recieves within it's event args a collection TraceContextRecord.

It can be used to log events on a sql server database.

First requires to run Aspnet_regsql.exe utility to create the db that will be used by listeners, Confiure SQL server for application Services, pick an instance to host on, you get a summary, and it will take care of confuring the database, now it's set to save health info on this db.

In the web.config, a healthMonitoring element needs to be added within the system.web eleement, by specifiying the provider, it's type, connection string, and then rules for which events to log, and EventMappings from the root Web.config file.




Comments

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.

Javascript: Closure and Lexical Scope

The two are separate topics, I just happen to put them in the same post for now. Closure Closure is the capability to remember it's lexical scope, even when executed outside it's lexical scope. If two inner functions, are within the same scope, they share the same closure.     Lexical scope The lexical scope is the scope in which a variable is declared during the first pass of the javascript compilation, which has two passes, compilation and execution. During the compilation pass, the compiler goes through the code looking for formal declaration, that is, var, function and parameters of function. For each of these formal declarations, the compiler will check the current lexical scope, and add this identifier if it isn't already there. Then at the second pass, execution, the compiler will run the code as we are intuitively use to and once it reaches the the identifiers found earlier, will ask if they are left hand side(RHS), or right hand side (LHS). If th...