WikiPage Getting started modified by Robajz

Robajz — Wed, 27 Feb 2013 18:11:57 -0000

--- v1
+++ v2
@@ -1,21 +1,20 @@
 I can imagine the description is not very suggestive. So I encourage you to drop a note in the forum and I'll try to get you sorted :o)

-This is a tool-kit, right? So it is not meant to provide a final solution to all your log processing needs ready made. You'll have to show some effort. You'll have to understand it and use it.
-Having said that, it is very simple and I'm ready to give you a hand if you run in troubles.
+This is a tool-kit, right? So it is not meant to provide a final solution to all your log processing needs ready made. You'll have to show some effort. You'll have to understand it and use it. Having said that, it is very simple and I'm ready to give you a hand if you run in troubles.

 1. Check the code out from trunk (use TortoiseSVN to make your life easier)
 svn co https://logharvester.svn.sourceforge.net/svnroot/logharvester/trunk/ logharvester
 * Compile the whole solution thing in VS2010 (Or SharpDevelop or Monodevelop)
 * Take a look at some of the existing sample tools, let's take the LH_General/bin/release
-    * Now the most important thing is LogHarvester.dll - it contains the units for log processing
+    1. Now the most important thing is LogHarvester.dll - it contains the units for log processing
     * Second most important thing is Scriptor.exe - it gives you the ability to run scripts (magically compiling them on the fly for you)
-    * There is also the XPathHelper.dll that is being used by both previous guys for XML configuration
+    1. There is also the XPathHelper.dll that is being used by both previous guys for XML configuration
     * Scriptor.script.cs is the script that will be run by Scriptor.exe
     * Scriptor.script.config is the final point of your interest. This is where you tell the tool-kit what to do.
     * The rest is not as important to get you started.
 * Modify the Scriptor.script.config to suit your needs.
-You should think of it as of a workflow. The data being a signal running through various components turning into diferent data and triggering actions. 
-Another point of view is a real life harvester you can see on the field gathering cereals for your family. It consists of different units ordered in a way to collect, extract, process and deliver things.
+    1. You should think of it as of a workflow. The data being a signal running through various components turning into diferent data and triggering actions. 
+    * Another point of view is a real life harvester you can see on the field gathering cereals for your family. It consists of different units ordered in a way to collect, extract, process and deliver things.
 * Now I really want to hear your questions... Do you find it any useful? 

 In my company, In one example I use it to process SQL server 2000 error log for deadlocks - understand to extract the information for further analysis and statistics and also to send and email alert. The logs are being processed as they're written every 15 minutes. The information extracted provides an important foundation for database admins and developers in resolving deadlock issues. Another example is a general ERROR reporting from the number of applications we have to manage.

WikiPage Getting started modified by Robajz

Robajz — Wed, 27 Feb 2013 18:06:12 -0000

I can imagine the description is not very suggestive. So I encourage you to drop a note in the forum and I'll try to get you sorted :o)

This is a tool-kit, right? So it is not meant to provide a final solution to all your log processing needs ready made. You'll have to show some effort. You'll have to understand it and use it.
Having said that, it is very simple and I'm ready to give you a hand if you run in troubles.

Check the code out from trunk (use TortoiseSVN to make your life easier)
svn co https://logharvester.svn.sourceforge.net/svnroot/logharvester/trunk/ logharvester
Compile the whole solution thing in VS2010 (Or SharpDevelop or Monodevelop)
Take a look at some of the existing sample tools, let's take the LH_General/bin/release
- Now the most important thing is LogHarvester.dll - it contains the units for log processing
- Second most important thing is Scriptor.exe - it gives you the ability to run scripts (magically compiling them on the fly for you)
- There is also the XPathHelper.dll that is being used by both previous guys for XML configuration
- Scriptor.script.cs is the script that will be run by Scriptor.exe
- Scriptor.script.config is the final point of your interest. This is where you tell the tool-kit what to do.
- The rest is not as important to get you started.
Modify the Scriptor.script.config to suit your needs.
You should think of it as of a workflow. The data being a signal running through various components turning into diferent data and triggering actions.
Another point of view is a real life harvester you can see on the field gathering cereals for your family. It consists of different units ordered in a way to collect, extract, process and deliver things.
Now I really want to hear your questions... Do you find it any useful?

In my company, In one example I use it to process SQL server 2000 error log for deadlocks - understand to extract the information for further analysis and statistics and also to send and email alert. The logs are being processed as they're written every 15 minutes. The information extracted provides an important foundation for database admins and developers in resolving deadlock issues. Another example is a general ERROR reporting from the number of applications we have to manage.

Happy harvesting!
Robert.

Recent changes to Getting started

WikiPage Getting started modified by Robajz

WikiPage Getting started modified by Robajz