I’m hoping to find something that:

  • has a nice dashboard
  • is quick and simple to install
  • is very lightweight and unobtrusive
  • can send alerts via http request
  • utopiah@lemmy.ml
    4·
    5 days ago

    send alerts via http request

    On this specifically you might want to check ntfy as it’s quite easy to setup and can give you notifications on pretty much any device (including iOS) via your own infrastructure all the way down to basics e.g. SSE. That mean you can subscribe to a topic, e.g. servers per physical location, alert level, etc and only get the ones you need.

  • notabot@lemm.ee
    51·
    6 days ago

    Nagios. It does depend on what you mean by monitor though. Nagios is good at telling you that “service A on host B” is down" but less useful for looking at things like performance trends. I particularly like being able to setup dependencies between services, so I get the alert for the root cause, and not all of the services that have gone down because of it.

  • tath@social.tath.link
    8·
    6 days ago

    Zabbix is pretty quick and easy. Many different services built in for sending notifications, along with your own custom (including webhooks). Fully customizable dashboard as well so you can add whatever you want/need at a glance.

  • hindy@mbin.lovetux.net
    21·
    6 days ago

    Hello,

    I’m still using Nagios here. And for the availability of the services I’m using uptime-kuma (in a docker).

  • sgh@lemmy.ml
    2·
    6 days ago

    While I use LibreNMS as it uses SNMP for monitoring (which is pretty much available everywhere), I don’t believe it has http alerts, but I know for a fact that it can send Telegram messages.

  • RegalPotoo@lemmy.worldEnglish
    10·
    6 days ago
    • Base ansible role installs Prometheus node exporter, configured with the text file collector
    • VM automations push DNS records so that the Prometheus dns-sd automatically discovers them
    • Ansible roles for add Cron jobs that generate metrics for specific systems and dump them for the text file collector
    • Grafana for dashboards
    • Karma as a UI in front of Prometheus alert manager
    • tetris11@lemmy.ml
      1·
      6 days ago

      Cron jobs that generate metrics for specific systems and dump them for the text file collector

      Details please

      • RegalPotoo@lemmy.worldEnglish
        2·
        5 days ago
        • https://github.com/prometheus/node_exporter?tab=readme-ov-file#textfile-collector - which makes node exporter watch a specific directory for files that contain metrics, then re-export them back to the central Prometheus server
        • Some systems have their own metrics endpoints - instead of getting Prometheus to scrape these directly I set up a Cron job to curl these into files for node exporter - this means I don’t need extra config in Prometheus to find the endpoints, and don’t need to mess with firewall rules
        • Other systems don’t directly expose metrics in a format Prometheus can use - in this case I will write/find a script that can do the conversation, then either set it up to write the metrics file directly and run it on a Cron, or run it as a service and another Cron job to do the scrape
    • Toribor@corndog.socialEnglish
      1·
      5 days ago

      Any chance you’d be willing to share playbooks or point me toward any resources you used?

      I use Ansible to manage config across all my workstations/servers but I haven’t gotten around to automating log shipping yet or aggregating system metrics.

  • ddh@lemmy.sdf.orgEnglish
    33·
    5 days ago

    I use my family. It has a simple volume based alert for when services are offline.

  • loganb@lemmy.world
    11·
    6 days ago

    I personally use CheckMK.

    • Offer a free “Raw” version.
    • Can be deployed with docker.
    • OSS

    One thing is that it can be a lot to take in at first and took me a while to get used to it.

    • corsicanguppy@lemmy.caEnglish
      2·
      5 days ago

      CheckMk user here via omd.

      I’m looking for something else after the upgrade.

      1. Black interface isn’t pretty for me and the old interface was “meh too hard so we ditched it”.

      2. One half of the project split has a shit supply chain and just doesn’t meet the bar for upgrade requirements.

      3. The other half of the project split is a mess to config in an automated desired-state setup. It’s all edge-triggered manual bullshit. NO. ENOUGH.

      I miss 1.2 .

    • hobbsc@lemmy.sdf.orgEnglish
      1·
      5 days ago

      checkmk user here. i can second the adjustment phase. i tend to ignore my servers but when something goes sideways it’s awesome to have checkmk’s structure in place.