LogViewPlus Support » LogViewPlus Support » Configuration & Customization » Post Processing

Post Processing

dv1sual — Thu, 17 Dec 2020 16:11:14 GMT

Good morning!

I edited the CustomParser template to adapt LogViewPlus to the type of my logs, and it works fine.
What I did there it just introduces the Priority based on some string in my log lines.

Now I would like to Implement a post-processor where if the message in the log entry contains the word "error" it changes the priority of the line to "Error".

In the CustomParser i would use this:

[code] newEntry.Priority = "Info";
if (logLine.Contains("error"))
{
newEntry.Priority = "Error";
}[/code]

But it's not working in the PostProcessor.
Any hint how do I do it?

Thanks in Advance for any advise!

RE: Post Processing

LogViewPlus Support — Thu, 17 Dec 2020 16:11:14 GMT

Glad to that helped. Thanks for letting me know. :-)

Toby

RE: Post Processing

dv1sual — Thu, 17 Dec 2020 16:09:48 GMT

Hi Toby,

you're a legend.

I didn't add the post-processor to the parser.
The code is working fine!

Thanks so much for your help, you made my day!

Cheers!

RE: Post Processing

LogViewPlus Support — Thu, 17 Dec 2020 16:04:46 GMT

Thanks for the update.

When you put a break point in your code, is it being called? Have you added the post processor to your parser configuration?

RE: Post Processing

dv1sual — Thu, 17 Dec 2020 16:02:06 GMT

Hi Toby,

When I'm saying is not working I mean that when I open up my log, all the lines that contain the word "test" are not changed to "Error" Priority, but they stay in "Info".

I'm compiling and launching it from Visual Studio, and I can see that my parser works fine (the log level are added to the log) but nothing from the PostProcessor side.

Thanks for your help so far.

RE: Post Processing

LogViewPlus Support — Thu, 17 Dec 2020 15:54:38 GMT

The code looks fine. When you say it doesn't work - what do you mean? How is it now working? Is your code being called?

I would suggest debugging to see if the OriginalLogEntry contains the text you are expecting.

Toby

RE: Post Processing

dv1sual — Thu, 17 Dec 2020 15:34:54 GMT

Hi Toby.

yes, was a compile error.
Now it compiles it, and it runs LogViewPlus, but it actually doesn't work.

But that's my problem, I think somewhere in the Parser.
Would you mind to look at the full Post Processor code and tell me if you think is all right?

[code]using Clearcove.LogViewer.Common;
using System;
using System.Collections.Generic;
using System.Configuration;
using System.Diagnostics;
using System.Globalization;
using System.Reflection;

namespace CustomPostProcessor
{

public class MyPostProcessor : ILogPostProcessor
{

public void Modify(LogEntry newEntry)
{

newEntry.Priority = "Info";
if (newEntry.OriginalLogEntry.Contains("test"))
{
newEntry.Priority = "Error";
}

}

}
}[/code]

Anything I'm missing that you can spot?

Thanks again for your patience.

L.

RE: Post Processing

LogViewPlus Support — Thu, 17 Dec 2020 14:07:46 GMT

That's interesting. It looks like a compile error rather than a runtime issue.

In your parser 'logLine' is a String. String objects have a Contains method.

In the finalizer, you receive a LogEntry. Not a String, but it does contain Strings. Try newEntry.OriginalLogEntry.Contains().

Hope that helps,

Toby

RE: Post Processing

dv1sual — Thu, 17 Dec 2020 13:33:57 GMT

Hi Toby,

yes, i'm doing the debugging in Visual Studio.
It gave me this:

[code]Error CS1061 'LogEntry' does not contain a definition for 'Contains' and no accessible extension method 'Contains' accepting a first argument of type 'LogEntry' could be found (are you missing a using directive or an assembly reference?)
[/code]

I used that code easily in Parser, but not editing the post-processing file.
I'm sorry if this sounds obvious, i just have little knowledge in C#.

Let me know if i can provide more info to being able to help you help me with this.

Thanks!

RE: Post Processing

LogViewPlus Support — Thu, 17 Dec 2020 12:58:44 GMT

Good Morning! :-)

From your description, this should be working fine. There should be no problem changing the Priority.

There are two things I would suggest:

1. Do not use the 'Message' field, use the 'OriginalLogEntry' field. The Message field is optional and will contain the result produced by the parser (if any). The OriginalLogEntry is required and contains the full text of the log entry.

2. Have you tried debugging your plug-in? The steps described in our documentation can be used to launch LogViewPlus from within Visual Studio. If you start LogViewPlus from a debugger, you should see your breakpoints being hit.

Hope that helps. Please let me know if you have any further questions or issues.

Toby