home.social

#smokeping — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #smokeping, aggregated by home.social.

  1. Can #Smokeping create a grouped view of some probes, that I can reference through targets?

  2. @dillo I got it running here now: smokeping.melroy.org/

    I just setup it up. Although I'm also running Grafana (Like: stats.melroy.org/public-dashbo)

    Smokeping has its own web interface. It should be feasible to create fping with influxdb/Prometheus and create graphs in Grafana as well. But for now I just setuped smokeping.melroy.org/

    #smokeping #ping #fping #opensource

  3. @dillo I there. There is another tool, which I like even more. It's called #fping and #smokeping github.com/oetiker/SmokePing. And they just released a new version v2.9.0: oss.oetiker.ch/smokeping/pub/s. Smokeping is using fping under the hood. You can also run fping solo.

    Anyhow, here are my results of just the ping command:

    --- google.com ping statistics ---
    100 packets transmitted, 100 received, 0% packet loss, time 20287ms
    rtt min/avg/max/mdev = 6.139/7.144/8.523/0.586 ms
  4. More progress on the #homelab renovation.. mostly software-related at the moment though. Managed to get #nomad to correctly mount the NFS volumes I needed for #smokeping and #mariadb, and figured out how template files work for simple config files being passed in to containers.

    I'm currently using my old #unraid server as the storage backend.. but I'll most likely still be upgrading to a new unraid server soon so what I setup now can easily be translated to the next server. Once I have everything transferred I'll setup a backup task across the storage on unraid so that I have all application states protected.

    Last thing to figure out is the load balancing for my services. I want them all accessible via IP/port on my LAN and by service under #tailscale. Not sure how this will all fit together - I probably need a dedicated box for the LB.. maybe just a simple #nginx proxy with #consul configuration so that it's somewhat dynamic. Would love to get feedback on this, and if you know of a simpler/better way!

  5. You can now find some #smokeping graph on #BoxyBSD's status page: boxybsd.com/status/

    Do you miss any destination? Let us know!

  6. I have more than enough technical hobby projects, and #HomeAutomation runs flawlessly with #HomeMatic/ #RaspberryMatic and #CUxD.

    But taking a look at #HomeAssistant as an umbrella front-end is definitively worthwhile. Tons of supported 3rd party systems and protocols, a flexible modern GUI, and a resource efficient #docker container are only a few advantages. Also helps to retire some obsolete services like, e.g. #SmokePing.

    github.com/home-assistant/dock

  7. J'ai installé un #smokeping sur un raspberry pour en faire un outil d'analyse portable.

    J'aimerais pouvoir avoir une vue de nom d'hôte sur les graphs, là où il y a juste un nombre. On peut voir dans le preview du lien en bas quel est l'hôte, mais je voudrais que ça soit visible directement dans le titre.

    J'ai cherché une variable d'hostname, mais j'ai pas trouvé...Des idées ?

  8. Awesome! Seems I've figured out most of #nomad's networking quirks and have #smokeping running, finally..

    Even managed to get NFS mounting configured over a CSI so I can host app data externally. All in #terraform!

  9. Another quick entry in my series on how and what I #SelfHost: #Monitoring

    #UptimeKuma monitors and alarms all of the services and hosts I run, #HealthChecks(.io) for monitoring and alarming cron jobs, and #SmokePing for network monitoring (no alarming). I've used #Pushover for years to deliver notifications to my phone, but I'm slowly switching things to #SelfHosted #Gotify

    With servers, laptops, and a ton of docker containers, I run network caches to be a good neighbour, and prevent duplicate requests to upstream repos when I'm doing updates, builds, or deployments. For Apt-based repositories, I use Apt-Cacher-NG, for Docker images (runs on swarm), I have a Docker Registry Mirror (runs on swarm), #DevPi as a #PyPi cache (on swarm), and I have Squid running on pfSense for the odd HTTP-cacheable content.

    🏷️ #SelfHosting

  10. Another quick entry in my series on how and what I #SelfHost: #Monitoring

    #UptimeKuma monitors and alarms all of the services and hosts I run, #HealthChecks(.io) for monitoring and alarming cron jobs, and #SmokePing for network monitoring (no alarming). I've used #Pushover for years to deliver notifications to my phone, but I'm slowly switching things to #SelfHosted #Gotify

    With servers, laptops, and a ton of docker containers, I run network caches to be a good neighbour, and prevent duplicate requests to upstream repos when I'm doing updates, builds, or deployments. For Apt-based repositories, I use Apt-Cacher-NG (runs on swarm), for Docker images, I have a Docker Registry Mirror (runs on swarm), #DevPi as a #PyPi cache (on swarm), and I have Squid running on pfSense for the odd HTTP-cacheable content.

    🏷️ #SelfHosting

  11. Another quick entry in my series on how and what I #SelfHost: #Monitoring

    #UptimeKuma monitors and alarms all of the services and hosts I run, #HealthChecks(.io) for monitoring and alarming cron jobs, and #SmokePing for network monitoring (no alarming). I've used #Pushover for years to deliver notifications to my phone, but I'm slowly switching things to #SelfHosted #Gotify

    With servers, laptops, and a ton of docker containers, I run network caches to be a good neighbour, and prevent duplicate requests to upstream repos when I'm doing updates, builds, or deployments. For Apt-based repositories, I use Apt-Cacher-NG (runs on swarm), for Docker images, I have a Docker Registry Mirror (runs on swarm), #DevPi as a #PyPi cache (on swarm), and I have Squid running on pfSense for the odd HTTP-cacheable content.

    🏷️ #SelfHosting

  12. Another quick entry in my series on how and what I #SelfHost: #Monitoring

    #UptimeKuma monitors and alarms all of the services and hosts I run, #HealthChecks(.io) for monitoring and alarming cron jobs, and #SmokePing for network monitoring (no alarming). I've used #Pushover for years to deliver notifications to my phone, but I'm slowly switching things to #SelfHosted #Gotify

    With servers, laptops, and a ton of docker containers, I run network caches to be a good neighbour, and prevent duplicate requests to upstream repos when I'm doing updates, builds, or deployments. For Apt-based repositories, I use Apt-Cacher-NG, for Docker images (runs on swarm), I have a Docker Registry Mirror (runs on swarm), #DevPi as a #PyPi cache (on swarm), and I have Squid running on pfSense for the odd HTTP-cacheable content.

    🏷️ #SelfHosting

  13. Back at the beginning of 2020 I spun up this #dns anycast test “framework” dns.qosbox.com
    Wondering if anyone in the #fediverse would like to cm tribute. It’s fairly low tech but it’s got several years of data at this point. If anyone is interested please reach out here!!

    #neteng #ipv6 #internet #smokeping #latency

  14. @jselea TIL #OmniOS Community Edition Association’s president is @oetiker, also developer of #RRDtool and the #Perl based #MRTG and #SmokePing

  15. I have a few devices running #Smokeping for fun and giggles. They are listed on smokeping.eu/.

  16. With these checkmk dashboards I can also retire my #smokeping container as well.

    #nms #checkmk #nagios