Local Filter CONTAINS always checks Stacktrace column

[arthuratplayableworlds]

I'm using Windows, in cmd.

At first I thought the local filtering just didn't work, but after playing with it, I've found some things... If I do a simple search, like "INFO", it will search for that text in all fields, as I'd expect. If I do Level CONTAINS "INFO", it returns no results (although I clearly have logs with Level INFO.)

Interestingly, if I do Level CONTAINS "Logger", I get results! But these results contain the word "Logger" in the "Stacktrace" column, not in the Level column.

This seems to be 100% consistent. If I do Message CONTAINS "Logger", I also get results where Stacktrace includes "Logger". So regardless of what column I specify in the filter, it always uses the stacktrace column.

In this screenshot you can see I'm checking if the timestamp contains Logger. Obviously, it doesn't. Here's the expanded log:

[aurc]

Thanks for the feedback, I will have a look and try to reproduce; in between if you could send a sample log would also be greatly appreciated. It could be related to some weird encoding therefore a sample file might be useful.

On Thu, 10 Oct 2024 at 5:55 am, Arthur @.***> wrote:

I'm using Windows, in cmd.

At first I thought the local filtering just didn't work, but after playing with it, I've found some things... If I do a simple search, like "INFO", it will search for that text in all fields, as I'd expect. If I do Level CONTAINS "INFO", it returns no results (although I clearly have logs with Level INFO.)

Interestingly, if I do Level CONTAINS "Logger", I get results! But these results contain the word "Logger" in the "Stacktrace" column, not in the Level column.

This seems to be 100% consistent. If I do Message CONTAINS "Logger", I also get results where Stacktrace includes "Logger". So regardless of what column I specify in the filter, it always uses the stacktrace column.

image.png (view on web) https://github.com/user-attachments/assets/6bb58ef7-3a82-4c8f-9070-d047ad940a2f

— Reply to this email directly, view it on GitHub https://github.com/aurc/loggo/issues/23, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANCU24C3NRUDVXNHZ3CYFFTZ2V33HAVCNFSM6AAAAABPVFSSX6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TMNZQGA2TMMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[aurc]

@arthuratplayableworlds, I could not reproduce, please provide a sample log, any template you're using to render the logs and I'll try reproducing again.

[arthuratplayableworlds]

I can't attach the template but this is its contents:

    - name: Timestamp
      type: string
      color:
        foreground: white
        background: black
      max-width: 24
    - name: Level
      type: string
      color:
        foreground: white
        background: black
      max-width: 6
      color-when:
        - match-value: ERROR
          color:
            foreground: orangered
            background: ""
        - match-value: WARN
          color:
            foreground: olive
            background: ""
        - match-value: FATAL
          color:
            foreground: aliceblue
            background: lavender
        - match-value: INFO
          color:
            foreground: cornflowerblue
            background: ""
        - match-value: DEBUG
          color:
            foreground: aquamarine
            background: ""
        - match-value: VERBOSE
          color:
            foreground: silver
            background: ""
    - name: Message
      type: string
      color:
        foreground: white
        background: black
      max-width: 100
    - name: Stacktrace
      type: string
      color:
        foreground: white
        background: black
      max-width: 10

and the log: log.txt

[arthuratplayableworlds]

@aurc updated