Try This


  1. Perform a log file assessment of your current system. What logs does it produce? Why? Who uses these logs? For what purpose? Are these logs secured? If not, do they need to be Are they plain text? If not, why not?

  2. How big are your logs? How much data are you generating?

  3. Is any data redundantly logged (e.g., a Web server is already logging some data)?

  4. Are logs unique to each day? Are they rolling?

  5. Open a sample log. Are there any "silly" entries relative to the target audience? An example would be the name of a function and all of its parameters in a log file designed for behavior tracking and analysis. Such an entry isn't useful to the marketect unless a postprocessing tool can convert it into an appropriate entry.



Beyond Software Architecture[c] Creating and Sustaining Winning Solutions
Beyond Software Architecture[c] Creating and Sustaining Winning Solutions
ISBN: 201775948
EAN: N/A
Year: 2005
Pages: 202

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net