By HeinA - 15 Oct 2025
'ello
I send events over Udp in Log4j format usin NLog from a MAUI application
Chainsaw receives the events, But LogViewPlus shows nothing. I much prefer LogViewPlus and would love to understand what I'm doing wrong
Thank you in advance
|
By LogViewPlus Support - 15 Oct 2025
Hi,
Thanks for reporting this issue.
The UDP listener is pretty straight-forward. It works by writing the data received into a file in your temp directory. From there, LogViewPlus opens and parses the temp file as normal.
If this isn't working, then either LogViewPlus isn't recieving the data or it is unable to parse the data received.
I can see you have already found the transfer log. I assume it didn't say anything useful?
If you right click on your "Maui" file and go to Properties, you should be able to see the local file. If you open the local file, does it have any data?
Thanks again,
Toby
|
By HeinA - 16 Oct 2025
Ok. The local file has some contents, but it does not reflect on the UI:
|
By LogViewPlus Support - 16 Oct 2025
That's good news - it means that the networking aspects of your configuration appear to be working correctly.
It looks like the problem is with parsing the log file. If you go into Settings -> Log Parsers -> Parser Mappings, you should see an entry which maps to a "localhost_4445" file. You will need to update this setting to apply the correct parser mapping.
From your screenshot, it looks like you just need to change it to use the Log4XmlParser:
It might help to first parse the file you have in your temp directory before retrying your UDP listener. This will break the problem into two parts.
Hope that helps,
Toby
|
By HeinA - 16 Oct 2025
'ello
I tried something like that:
I have the following:
If I try and add another for localhost_4445, I get an error
|
By HeinA - 16 Oct 2025
OK....
I first had to delete my Datas Source:
then I could add a mapping:
Then I re-added the Data Source
now I'm getting the events:
Thanx for your help!
|
By LogViewPlus Support - 16 Oct 2025
Excellent! Thanks for letting me know. 
In this case, the datasource and parser configuration are working together. You could have configured them manually to make that collaboration work, but deleting and recreating works too.
I think there may have been some confusion because you were modifying the "Basic Parser" - which is an existing parser. Usually, when you want to parse a new file, you create a new parser configuration rather than editing an existing one.
Thanks again,
Toby
|
By HeinA - 16 Oct 2025
Yes.. I tried creating a new Parser, but I kept getting the "Configuration name already in use error"
Only once I deleted the data source, could I create a parser with the correct pattern
|
By LogViewPlus Support - 16 Oct 2025
Thanks for the update.
The "Configuration name already in use" error message you saw is expected. Each parser configuration in LogViewPlus must have a unique configuration name.
My guess is that when you tried to create a new parser, you may have inadvertently used a name that was already in use, such as "Basic Parser".
Let me know if that makes sense or if you run into any other issues.
Toby
|