By Hyunbin - 25 Oct 2024
Hi,
I have such this format of data. I noticed that the data cannot be parsed because of the 20 digits of value. It can't ignore the properties contents to be parsed. Do you have an idea what I did wrong?
{
"@t": "date",
"@l": "Information",
"@m": "Contents",
"@mt": "Contents",
"Properties": {
"Some1": 42,
"Some2": 1,
"value": 12312312312312312312,
"Some3": "AIM",
"Some4": 42,
"Some5": "x.x.x.x",
"Some6": 1,
"Some7": "xx"
}
}
---------------------------------------------------------------------
The format I tried to parse :
{
"@t": "%d{yyyy-MM-ddTHH:mm:ss.fffffffzzzz}",
"@l": "%p",
"@m": "%m",
"@mt": "%m{-parserhint:CLEF}",
"Properties": "%s"
}
Hyunbin
|
By LogViewPlus Support - 27 Oct 2024
Hi Hyunbin,
Thanks for reporting this issue. After investigation, I have been able to recreate the isue and can confirm the bug.
This error is due to not using a special compilier flag in the JSON.Net library that we use. I have resolved the issue and it will be fixed in the next release. We hope to have a BETA release out early next week. I will post back here when it is available.
Thanks again!
Toby
|
By Hyunbin - 28 Oct 2024
Thank you for the quick response!
|
By LogViewPlus Support - 3 Dec 2024
Hi Hyunbin,
I just wanted to let you know that we have now released LogViewPlus v3.1.16 as a BETA release which addresses the JSON paring issue discussed above.
Thanks again for bringing this issue to our attention. Please do let me know if you have any further questions or issues.
Toby
|
|