	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.6

Microsoft Enterprise Library stackTrace log file grows endlessly.

Asked by carl- in Microsoft Programming, Microsoft Visual C#.Net, .NET

Tags: microsoft enterprise library stackTrace log file

Hi all,
My company uses the Microsoft Enterprise Library to log exceptions to a stacktrace log file. The problem I have with doing this is that no one ever clears out the log file and we end up with this huge multi-megabyte file in my c:\logs\ directory after a year.
What are other people doing to log long running server programs exceptions to a file, yet clear out records older than x days, or after x number of megabytes? 3rd party programs? different code?
Any thoughts would help.
Thanks

Here is code excerpt that controls TraceLog.TraceMessage
LogEntry logEntry = new LogEntry();
logEntry.Categories.Clear();
logEntry.Categories.Add("Trace");
logEntry.Priority = 5;
logEntry.Severity = TraceEventType.Information;
logEntry.Message = Message + Environment.NewLine + Environment.NewLine;
Logger.Write(logEntry);

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:

           
           
             <loggingConfiguration name="Logging Application Block" tracingEnabled="true"
    defaultCategory="General" logWarningsWhenNoCategoriesMatch="false">
    <listeners>
      <add source="MyCompanyexe" formatter="Event Formatter" log="" machineName="."
        listenerDataType="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.FormattedEventLogTraceListenerData, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        traceOutputOptions="None" type="Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.FormattedEventLogTraceListener, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        name="Event Log Destination" />
      <!-- TraceLog output Filename below-->
      <add fileName="C:\logs\XmlExport_trace.log" header="" footer=""
        formatter="Text Formatter" listenerDataType="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.FlatFileTraceListenerData, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        traceOutputOptions="None" type="Microsoft.Practices.EnterpriseLibrary.Logging.TraceListeners.FlatFileTraceListener, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        name="Flat File Destination" />
    </listeners>
    <formatters>
      <add template="Timestamp: {timestamp};&#xA; Message:{message};&#xA; Category:{category};&#xA; Priority: {priority};&#xA; EventId:{eventid};&#xA;        Severity: {severity};&#xA;        Title:{title};&#xA;        Machine:{machine};&#xA;        Application Domain: {appDomain};&#xA;        Process Name:{processName};&#xA;        Extended Properties: {dictionary({key}  {value};)}"
        type="Microsoft.Practices.EnterpriseLibrary.Logging.Formatters.TextFormatter, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        name="Event Formatter" />
      <add template="Timestamp: {timestamp} Message: {message}" type="Microsoft.Practices.EnterpriseLibrary.Logging.Formatters.TextFormatter, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        name="Text Formatter" />
    </formatters>
    <logFilters>
      <add categoryFilterMode="AllowAllExceptDenied" type="Microsoft.Practices.EnterpriseLibrary.Logging.Filters.CategoryFilter, Microsoft.Practices.EnterpriseLibrary.Logging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null"
        name="Category" />
    </logFilters>
    <categorySources>
      <add switchValue="All" name="Error">
        <listeners>
          <add name="Event Log Destination" />
        </listeners>
      </add>
      <add switchValue="All" name="General">
        <listeners>
          <add name="Flat File Destination" />
        </listeners>
      </add>
      <add switchValue="All" name="Trace">
        <listeners>
          <add name="Flat File Destination" />
        </listeners>
      </add>
    </categorySources>
    <specialSources>
      <allEvents switchValue="All" name="All Events" />
      <notProcessed switchValue="All" name="Unprocessed Category" />
      <errors switchValue="All" name="Logging Errors &amp; Warnings">
        <listeners>
          <add name="Event Log Destination" />
        </listeners>
      </errors>
    </specialSources>
  </loggingConfiguration>

           
         

20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. Idle_Mind42,073
2. capricorn136,800
3. jpaulino34,380
4. Dhaest32,375
5. TheLearn...31,625
6. DanRollins31,510
7. boag200026,300
8. jkr21,550
9. abel21,290
10. chris_bot...20,900
11. BlueDevilF...18,800
12. itsmeandn...18,600
13. rorya18,400
14. CodeCruiser17,822
15. emoreau17,150
16. matthews...16,300
17. GrahamSkan16,200
18. LSMCons...15,100
19. jaime_oliv...13,948
20. tbsgadi13,700
21. DatabaseMX12,800
22. AndyAins...12,540
23. ged32512,400
24. Chris-Dent11,400
25. nutsch10,500

1. jkr264,770
2. capricorn1129,942
3. TheLearn...127,253
4. DanRollins102,780
5. AlexFM95,533
6. Idle_Mind90,025
7. LSMCons...69,314
8. jaime_oliv...68,398
9. naveenko...63,597
10. AndyAins...61,519
11. x_com60,518
12. emoreau59,403
13. DatabaseMX59,317
14. Arthur_...58,035
15. BlueDevilF...56,569
16. itsmeandn...56,036
17. Dhaest53,618
18. GrahamSkan53,209
19. angelIII52,996
20. PaulHews52,901
21. TimCottee50,191
22. jpaulino46,580
23. rorya45,600
24. nauman_...45,461
25. matthews...43,225

Microsoft Enterprise Library stackTrace log file grows endlessly.

Asked by carl- in Microsoft Programming, Microsoft Visual C#.Net, .NET

Tags: microsoft enterprise library stackTrace log file

About this solution