Hello,
Sorry if this is the wrong channel, but I couldn't find another way to reach out to you. I need to analyze some log files for a critical application I support, and your app seems to be just what I need. However, I am stuck at the "Conversion Pattern:" section of adding a log resource. I tried to input the conversion pattern in a few different ways, after reading your user manual, but the next button never becomes clickable, so I assume I am doing it wrong. Here is how the pattern layout is defined in our config file:
<layout type="FlexNet.SystemServices.Logging.Layout.PatternLayout">
<param name="ConversionPattern" value="%date %level %thread %property{EmployeeNo} %property{ClientId} %property{ProcessingContext} %logger %n %message%n%n" />
</layout>
Here is a sample of my log file:
2012-11-30 03:10:07,923 ERROR 23 System (null) JobId: 120912255 FlexNet.SystemServices.Xml.Configurations.RoutingConfigurationReader.CheckXPathExpression
Failed to Interpret XPath Expression /FlexNet.BusinessFacade.Inventory.InventoryAdjustController.Adjust/FlexNet.BusinessRules.Inventory.InventoryAdjuster.Adjust/Containers/Inventories/HostIndicator1 with value NOUPLOAD.
I'm sure I am just missing something. Please let me know what to do to get this to work. If this works for me it will save me hundreds of hours a month digging through log files manually.
Thanks!
-Josh-
Anonymous
Hi Josh! Right now, having one log entry that spans multiple lines is not supported. However, I will see what I can do for you. Please send me a sample with 10 to 20 events to philippn AT gmail DOT com or attach it to this issue (if you are allowed to).
Thanks in advance!
Here you go. Thanks so much for the help!
Hey Josh,
I have got a partial solution up and running. Partial in that it can parse the log events correctly but the portion "System (null) OperationId: 100001797" is put into a single field, the NDC.
I will fix this by implementing proper support for MDC, which was also requested some time ago. But I will need a bit more time for that.
In the meantime, I could offer you a development version that should get you going. Please let me know which flavour you would like (win32 x64, macos, whatever) and then I will upload the bits somewhere.
Mac OSX would be wonderful. Thanks again so much, you are saving me hours of work here.
Once I download it, how do I enter the Pattern Layout?
Hi again,
here is the link: http://netload.in/dateiSFH35R9NDp/net.sf.logsaw.app-macosx.cocoa.x86_64.zip.htm
Then try this pattern: %d{yyyy-MM-dd HH:mm:ss,SSS} %p %t %x %c%n %m%n%n
Hope that helps!
:-( This one won't even lauch. I am running Mountain Lion on a 15" MacBook Retina. Does that make a difference?
I guess you are running a 32 bit kernel then?! If so, try this: http://netload.in/dateiyAEHJPlIFJ/net.sf.logsaw.app-macosx.cocoa.x86.zip.htm
If you are running 64 bit, then the macos builds are probably broken and I will need some more specific information (.log file from the logsaw /workspace/.metadata dir).
Hope that helps!
Definitely running 64-bit:
jdesh00000-MR:~ jdesherlia$ uname -a
Darwin jdesh00000-MR.local 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
I'm emailing you the .log file. Subject will be
logsaw .log file from Josh
Thanks again! Sorry to be such a pain.
-Josh-
Definitely running 64-bit:
jdesh00000-MR:~ jdesherlia$ uname -a
Darwin jdesh00000-MR.local 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
I'm emailing you the .log file. Subject will be
logsaw .log file from Josh
Thanks again! Sorry to be such a pain.
-Josh-
Hey Josh, sorry to hear that! I have recently switched the build system and probably the MacOS builds are broken since :-( I have no Mac available, so I can't test myself and the log file you sent seems ok.
You could try copying over the .exe and .ini file from the 1.0.3 release, maybe that helps. I will check wether the Linux bits work. If Linux is also broken, maybe the root cause is the same as with MacOS (well, at least I hope so).
Hope that helps!
Note to self: Issue is probably related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=355370
Thanks. Let me know if you want me to help you test. I'd be happy to assist.
Ok, here is another build. This time build on a unix machine.
http://netload.in/datei4YLiLof92k/net.sf.logsaw.app-macosx.cocoa.x86_64.tar.gz.htm
Please let me know if that works.
Thanks in advance!