[BUG] LogMonitor config parser sensitive to order of waitInSeconds property in JSON

[mloskot]

Describe the bug

Depending on order of waitInSeconds property, configuration file is parsed as valid or invalid.

To Reproduce

Steps to reproduce the behavior:

1. Create nonworking.json with waitInSeconds ordered this way:

   {
     "LogConfig": {
       "sources": [
         {
           "type": "File",
           "filter": "*.log",
           "directory": "C:\\data\\Logs",
           "waitInSeconds": 0,
           "includeSubdirectories": false,
           "includeFileNames": false
         }
       ]
     }
   }

2. Run C:\LogMonitor.exe /config C:\nonworking.json an observe parsing error

   [2025-07-10T22:17:01.000Z][LOGMONITOR] ERROR: Failed to read json configuration file. JsonFileParser: Error at end of an object.
   [2025-07-10T22:17:01.000Z][LOGMONITOR] ERROR: Invalid configuration file.

3. Create working.json with waitInSeconds moved to the end of the object:

   {
     "LogConfig": {
       "sources": [
         {
           "type": "File",
           "filter": "*.log",
           "directory": "C:\\data\\Logs",
           "includeSubdirectories": false,
           "includeFileNames": false,
           "waitInSeconds": 0
         }
       ]
     }
   }

4. Run C:\LogMonitor.exe /config C:\working.json an observe all working

   [2025-07-10T22:15:42.000Z][LOGMONITOR] ERROR: Error in log file monitor. Failed to query file information. File: \\?\C:\data\Logs\seq-20250710.log. Error: 50
   [2025-07-10T22:15:42.000Z][LOGMONITOR] ERROR: Error in log file monitor. Failed to query file information. File: \\?\C:\data\Logs\seq-20250710.log. Error: 50

   (Those ERROR-s annoyance is benign, see Getting ERROR: Error in log file monitor. Failed to query file information [BUG] #125 (comment))

Expected behavior

The nonworking.json successfully parsed as a valid JSON.

Screenshots

n/a

Configuration
-Tool: Log Monitor
-Version: 2.1.1 (latest)

Additional context

n/a

[bobsira]

This must be related to the other bug I supposed

[mloskot]

@bobsira Sorry, I'm a bit lost, what is the other bug you mean?

[bobsira]

sorry for the confusion, since you mentioned bug #125 I thought they were related. Looking into this. Hopefully we can release the fix for both this issues and bug #125 together

[bobsira]

Hey @mloskot

I've put up a PR here: #215 to address the two concerns you said.

Here is a link to the exe with the changes: https://minikubevhdimagebuider.blob.core.windows.net/versions/LogMonitor.exe

Let me know if the issues still persist on your end in the new exe. I've tested on my end and everything looks fine.

Thanks.

[mloskot]

Hey @bobsira

See my comment #215 (comment)

By the way, your LogMonitor.exe from the link above reports LogMonitor Tool Version 2.1 - an outdated version number, but I assume that is fine.

[bobsira]

This issue is now fixed in this PR -> #217

@mloskot could you please help with approving the new PR. thanks!

[mloskot]

@bobsira Sure, done in #217 (review)

[bobsira]

Closing this since we've addressed it!