In looking for an app to view logs that doesn’t require a lot of overhead, I stumbled upon Logwatch. After running it through it’s paces, it seems to be pretty capable from docker, fail2ban, to sys logs.

I got to wondering if there are other such log viewers I could try that are in the same genre. Logwatch doesn’t greate pretty graphics and dialed out dashboards, but it’s fairly quick, I can view from a range of dates and times, and a variety of logs.

I checked out GoAcces, but it seemed geared towards web related logs like webpage hits, etc. With other options requiring elastisearch, databases, etc, they just seemed heavy for my application.

Anyone have any suggestions. So far, Logwatch does what it says on the tin, but I’m curious what others have tried or still use.

  • tuckerm@feddit.online
    link
    fedilink
    English
    arrow-up
    6
    ·
    10 hours ago

    I installed Grafana, simply because it was the only one I had heard of, and I figured that becoming familiar with it was probably useful from a professional development standpoint.

    It’s definitely massive overkill for my use case, though, and I’m looking to replace it with something else.

    • Xanza@lemm.ee
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      14 hours ago

      lmao this is exactly what I’ve been lookin for… Thanks! I just knew if I was a lazy fuck and sat on my hands someone would do the work for me eventually!

    • kernel_panic@feddit.uk
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 hours ago

      I can attest to Lnav being great, short of implementing a full Grafana/Loki stack (which is what i use for most of my infrastructure).

      Lnav makes log browsing/filtering in the terminal infinitely more enjoyable.

      • irmadlad@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        I can attest to Lnav being great

        I’m sitting here running it through some logs. So far, it’s on top of the stack.

  • fubarx@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    13 hours ago

    Saw a posting this past week on SSD drive failures. They’re blaming a lot of it on ‘over-logging’ – too much writing trivial, unnecessary data to logs. I imagine it gets worse when realtime data like OpenTelemetry get involved.

    Until I saw that, never thought there was such a thing as ‘too much logging.’ Wonder if there are any ways around it, other than putting logs on spinny disks.

    • irmadlad@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 hours ago

      Oh I’m not moving that much data to log, and the logs I read are all the normal stuff, nothing exotic. I guess if it were a huge cooperation, that had every Nagios plugin known to man and logging/log-rotating that because of logs, yeah I guess.

  • non_burglar@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    13 hours ago

    Wow, you just gave me flashbacks to my first Linux/unix job in 2008. Tripwire and logwatch reports to review every morning.