What’s the best way to monitor and log which processes are responsible for high system load throughout the day? Tools like top and htop only provide immediate values, but I’m looking for a solution that offers historical data to identify the main culprits over time.

@sysadmin

#sysadmin #linux #server

  • gravitas_deficiency@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    2 months ago

    Eesh. Yeah, that’s a nope from me, dawg.

    Actually, it’s all self-hosted. Granted, I haven’t looked at the code in detail, but building NNs to help efficiently detect and capture stuff is actually a very appropriate use of ML. This project looks kinda cool.

    • Onno (VK6FLAB)@lemmy.radio
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      2 months ago

      Machine Learning might be marketed as “all fine and dandy”, but I’m not planning on running a monitor training system loose on my production server under any circumstances.

      Not to mention that for it to be useful I’d have to give it at least a year of logs, which is both impossible and pointless, since the system running a year ago is not remotely the same as the one running today, even if not a single piece of our own code changed, which of course it did, the OS, applications and processes have been continually updated by system updates and security patches.

      So, no.

      • gravitas_deficiency@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        That’s why I put in the caveat about looking at the code. If you can’t grok what’s going on, that’s fine, but someone who does get it and can comfortably assert that no sketchy “phone home” shit is going on can and should use stuff like this, if they’re so inclined.