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

70-562 ListView

List View is a versatile control that allows to work with a signle control rather than many smaller controls. Provides rich sorting, deleting, editing, it is one of the most flexible grid control. Design view can fill the ListView with fake data to give an overview. In designer, the configure list view link might not show, (currently a bug), to fix configure the datasource but cancel then click configure datasource again and this time click finish and the Cofnoigure ListView link will show up in the smarttag. You can choose templates, LayoutTemplate is crucial, ItemTemplate(a row is part of a table, in a list view they are called items since they don't have to correspond to a table row), AlternatingItemTemplate, ItemSeparatorTemplate, SelectedItem, EmptyItemTemplate, EditItemTemplate, InsertItemTemplate allows to customize what the user will be presented when creating an item, EmptyDataTemplate. The itemPlaceHolder and the groupPlaceHolder are important elements as the will b...

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.

70-562 Tracing

Tracing can be enabled from the page directive, programmatically or from the web.config. This will append the trace info to the bottom of the page. There several tables of grouped trace information: Life cycle events, controls used by page, sessions state, cookies, http reuqest headers, server variables. SessionID, Time spent in each event, and check that the events are executing in the expected order. The control tree give a hierarchy of the controls in the page, and how much the control is using in the viewstate, and render by tells how much room the control uses on the page. See cookie information. And can see the Header information incase you do any kind of header manipulation. Also see query string collection. Also see the server variables passed back and forth between the server and the client application, logon user, remote user. Enable tracing when not in production, (remember to disable it when building a release... that and the debug= true setting get forg...