diff options
| -rw-r--r-- | about/resources.md | 200 | ||||
| -rw-r--r-- | gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md | 2 | ||||
| -rw-r--r-- | gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.md | 621 | ||||
| -rw-r--r-- | index.md | 2 | ||||
| -rw-r--r-- | uptime-stats.md | 28 |
5 files changed, 116 insertions, 737 deletions
diff --git a/about/resources.md b/about/resources.md index ec9379d9..7e971f7f 100644 --- a/about/resources.md +++ b/about/resources.md @@ -35,54 +35,54 @@ You won't find any links on this site because, over time, the links will break. In random order: -* Concurrency in Go; Katherine Cox-Buday; O'Reilly -* The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress -* Developing Games in Java; David Brackeen and others...; New Riders -* Site Reliability Engineering; How Google runs production systems; O'Reilly -* The Pragmatic Programmer; David Thomas; Addison-Wesley * Programming Perl aka "The Camel Book"; Tom Christiansen, brian d foy, Larry Wall & Jon Orwant; O'Reilly -* Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly -* Perl New Features; Joshua McAdams, brian d foy; Perl School -* Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf +* Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press +* 97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly +* Developing Games in Java; David Brackeen and others...; New Riders +* The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional * Raku Recipes; J.J. Merelo; Apress -* Modern Perl; Chromatic ; Onyx Neon Press * C++ Programming Language; Bjarne Stroustrup; -* Terraform Cookbook; Mikael Krief; Packt Publishing -* 100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications -* Higher Order Perl; Mark Dominus; Morgan Kaufmann -* Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson +* Programming Ruby 3.3 (5th Edition); Noel Rappin, with Dave Thomas; The Pragmatic Bookshelf +* Funktionale Programmierung; Peter Pepper; Springer +* Ultimate Go Notebook; Bill Kennedy * Chaos Engineering - System Resiliency in Practice; Casey Rosenthal and Nora Jones; eBook +* Systems Performance Tuning; Gian-Paolo D. Musumeci and others...; O'Reilly +* Java ist auch eine Insel; Christian Ullenboom; +* The Practise of System and Network Administration; Thomas A. Limoncelli, Christina J. Hogan, Strata R. Chalup; Addison-Wesley Professional Pro Git; Scott Chacon, Ben Straub; Apress +* The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible +* Higher Order Perl; Mark Dominus; Morgan Kaufmann +* The Docker Book; James Turnbull; Kindle +* 21st Century C: C Tips from the New School; Ben Klemens; O'Reilly +* Polished Ruby Programming; Jeremy Evans; Packt Publishing * Amazon Web Services in Action; Michael Wittig and Andreas Wittig; Manning Publications -* Leanring eBPF; Liz Rice; O'Reilly -* The Go Programming Language; Alan A. A. Donovan; Addison-Wesley Professional -* DNS and BIND; Cricket Liu; O'Reilly -* Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly -* Data Science at the Command Line; Jeroen Janssens; O'Reilly +* Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly +* 100 Go Mistakes and How to Avoid Them; Teiva Harsanyi; Manning Publications +* Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press +* Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner +* The Kubernetes Book; Nigel Poulton; Unabridged Audiobook * Clusterbau mit Linux-HA; Michael Schwartzkopff; O'Reilly * Seeking SRE: Conversations About Running Production Systems at Scale; David N. Blank-Edelman; eBook +* DNS and BIND; Cricket Liu; O'Reilly +* Systemprogrammierung in Go; Frank Müller; dpunkt +* Modern Perl; Chromatic ; Onyx Neon Press * DevOps And Site Reliability Engineering Handbook; Stephen Fleming; Audible -* Object-Oriented Programming with ANSI-C; Axel-Tobias Schreiner +* Site Reliability Engineering; How Google runs production systems; O'Reilly +* Pro Puppet; James Turnbull, Jeffrey McCune; Apress +* Effective awk programming; Arnold Robbins; O'Reilly +* Terraform Cookbook; Mikael Krief; Packt Publishing * Go Brain Teasers - Exercise Your Mind; Miki Tebeka; The Pragmatic Programmers -* Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt -* 97 things every SRE should know; Emil Stolarsky, Jaime Woo; O'Reilly -* The Kubernetes Book; Nigel Poulton; Unabridged Audiobook +* Concurrency in Go; Katherine Cox-Buday; O'Reilly +* Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers * The KCNA (Kubernetes and Cloud Native Associate) Book; Nigel Poulton -* Funktionale Programmierung; Peter Pepper; Springer -* 21st Century C: C Tips from the New School; Ben Klemens; O'Reilly -* The DevOps Handbook; Gene Kim, Jez Humble, Patrick Debois, John Willis; Audible -* Kubernetes Cookbook; Sameer Naik, Sébastien Goasguen, Jonathan Michaux; O'Reilly -* The Docker Book; James Turnbull; Kindle +* Perl New Features; Joshua McAdams, brian d foy; Perl School * Raku Fundamentals; Moritz Lenz; Apress -* Learn You Some Erlang for Great Good; Fred Herbert; No Starch Press -* Effective awk programming; Arnold Robbins; O'Reilly +* Distributed Systems: Principles and Paradigms; Andrew S. Tanenbaum; Pearson +* Data Science at the Command Line; Jeroen Janssens; O'Reilly +* Leanring eBPF; Liz Rice; O'Reilly +* The Pragmatic Programmer; David Thomas; Addison-Wesley * Effective Java; Joshua Bloch; Addison-Wesley Professional -* Java ist auch eine Insel; Christian Ullenboom; -* Tmux 2: Productive Mouse-free Development; Brain P. Hogan; The Pragmatic Programmers -* Polished Ruby Programming; Jeremy Evans; Packt Publishing -* Ultimate Go Notebook; Bill Kennedy -* Pro Puppet; James Turnbull, Jeffrey McCune; Apress -* Systemprogrammierung in Go; Frank Müller; dpunkt -* Learn You a Haskell for Great Good!; Miran Lipovaca; No Starch Press +* Think Raku (aka Think Perl 6); Laurent Rosenfeld, Allen B. Downey; O'Reilly +* Hands-on Infrastructure Monitoring with Prometheus; Joel Bastos, Pedro Araujo; Packt ## Technical references @@ -90,55 +90,55 @@ I didn't read them from the beginning to the end, but I am using them to look up * Understanding the Linux Kernel; Daniel P. Bovet, Marco Cesati; O'Reilly * BPF Performance Tools - Linux System and Application Observability, Brendan Gregg; Addison Wesley -* Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley * The Linux Programming Interface; Michael Kerrisk; No Starch Press -* Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly +* Algorithms; Robert Sedgewick, Kevin Wayne; Addison Wesley * Implementing Service Level Objectives; Alex Hidalgo; O'Reilly -* Go: Design Patterns for Real-World Projects; Mat Ryer; Packt * Relayd and Httpd Mastery; Michael W Lucas +* Groovy Kurz & Gut; Joerg Staudemeier; O'Reilly +* Go: Design Patterns for Real-World Projects; Mat Ryer; Packt ## Self-development and soft-skills books In random order: -* Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook -* The Complete Software Developer's Career Guide; John Sonmez; Unabridged Audiobook -* The Good Enough Job; Simone Stolzoff; Ebury Edge -* 101 Essays that change the way you think; Brianna Wiest; Audiobook -* The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books -* Deep Work; Cal Newport; Piatkus -* Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly -* The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd -* The Joy of Missing Out; Christina Crook; New Society Publishers -* The Courage to Be Disliked; Ichiro Kishimi and Fumitake Koga; Audiobook -* Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion -* Ultralearning; Anna Laurent; Self-published via Amazon -* Meditation for Mortals, Oliver Burkeman, Audiobook -* The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select -* Influence without Authority; A. Cohen, D. Bradford; Wiley -* Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook -* The Software Engineer's Guidebook: Navigating senior, tech lead, and staff engineer positions at tech companies and startups; Gergely Orosz; Audiobook -* So Good They Can't Ignore You; Cal Newport; Business Plus +* The Bullet Journal Method; Ryder Carroll; Fourth Estate * The Off Switch; Mark Cropley; Virgin Books (RE-READ 1ST TIME) -* Soft Skills; John Sommez; Manning Publications -* Stop starting, start finishing; Arne Roock; Lean-Kanban University -* Digital Minimalism; Cal Newport; Portofolio Penguin * Slow Productivity; Cal Newport; Penguin Random House -* Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing -* The Bullet Journal Method; Ryder Carroll; Fourth Estate -* The Power of Now; Eckhard Tolle; Yellow Kite * 97 Things Every Engineering Manager Should Know; Camille Fournier; Audiobook +* The Phoenix Project - A Novel About IT, DevOps, and Helping your Business Win; Gene Kim and Kevin Behr; Trade Select +* Solve for Happy; Mo Gawdat (RE-READ 1ST TIME) +* The Power of Now; Eckhard Tolle; Yellow Kite +* Influence without Authority; A. Cohen, D. Bradford; Wiley +* Eat That Frog; Brian Tracy * The 7 Habits Of Highly Effective People; Stephen R. Covey; Simon & Schuster UK -* Ultralearning; Scott Young; Thorsons +* So Good They Can't Ignore You; Cal Newport; Business Plus +* The Daily Stoic; Ryan Holiday, Stephen Hanselman; Profile Books +* Meditation for Mortals, Oliver Burkeman, Audiobook * Eat That Frog!; Brian Tracy; Hodder Paperbacks +* Coders at Work - Reflections on the craft of programming, Peter Seibel and Mitchell Dorian et al., Audiobook +* Getting Things Done; David Allen +* Digital Minimalism; Cal Newport; Portofolio Penguin +* The Joy of Missing Out; Christina Crook; New Society Publishers +* Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press +* Staff Engineer: Leadership beyond the management track; Will Larson; Audiobook +* 101 Essays that change the way you think; Brianna Wiest; Audiobook +* Soft Skills; John Sommez; Manning Publications +* Time Management for System Administrators; Thomas A. Limoncelli; O'Reilly +* Who Moved My Cheese?; Dr. Spencer Johnson; Vermilion * Never Split the Difference; Chris Voss, Tahl Raz; Random House Business * Atomic Habits; James Clear; Random House Business -* Eat That Frog; Brian Tracy -* Getting Things Done; David Allen -* Solve for Happy; Mo Gawdat (RE-READ 1ST TIME) +* The Courage to Be Disliked; Ichiro Kishimi and Fumitake Koga; Audiobook * Psycho-Cybernetics; Maxwell Maltz; Perigee Books -* Consciousness: A Very Short Introduction; Susan Blackmore; Oxford Uiversity Press +* The Good Enough Job; Simone Stolzoff; Ebury Edge +* The Software Engineer's Guidebook: Navigating senior, tech lead, and staff engineer positions at tech companies and startups; Gergely Orosz; Audiobook +* The Complete Software Developer's Career Guide; John Sonmez; Unabridged Audiobook +* Stop starting, start finishing; Arne Roock; Lean-Kanban University +* Ultralearning; Scott Young; Thorsons +* Buddah and Einstein walk into a Bar; Guy Joseph Ale, Claire Bloom; Blackstone Publishing * Search Inside Yourself - The Unexpected path to Achieving Success, Happiness (and World Peace); Chade-Meng Tan, Daniel Goleman, Jon Kabat-Zinn; HarperOne +* Deep Work; Cal Newport; Piatkus +* The Obstacle Is The Way; Ryan Holiday; Profile Books Ltd +* Ultralearning; Anna Laurent; Self-published via Amazon [Here are notes of mine for some of the books](../notes/index.md) @@ -146,30 +146,30 @@ In random order: Some of these were in-person with exams; others were online learning lectures only. In random order: -* The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online * Developing IaC with Terraform (with Live Lessons); O'Reilly Online -* Structure and Interpretation of Computer Programs; Harold Abelson and more...; -* Ultimate Go Programming; Bill Kennedy; O'Reilly Online -* MySQL Deep Dive Workshop; 2-day on-site training +* Protocol buffers; O'Reilly Online +* The Well-Grounded Rubyist Video Edition; David. A. Black; O'Reilly Online +* Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training * AWS Immersion Day; Amazon; 1-day interactive online training +* Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need) * Cloud Operations on AWS - Learn how to configure, deploy, maintain, and troubleshoot your AWS environments; 3-day online live training with labs; Amazon -* Protocol buffers; O'Reilly Online -* The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online -* F5 Loadbalancers Training; 2-day on-site training; F5, Inc. +* Ultimate Go Programming; Bill Kennedy; O'Reilly Online +* Structure and Interpretation of Computer Programs; Harold Abelson and more...; * Apache Tomcat Best Practises; 3-day on-site training * Scripting Vim; Damian Conway; O'Reilly Online -* Linux Security and Isolation APIs Training; Michael Kerrisk; 3-day on-site training -* Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online +* MySQL Deep Dive Workshop; 2-day on-site training * Functional programming lecture; Remote University of Hagen -* Red Hat Certified System Administrator; Course + certification (Although I had the option, I decided not to take the next course as it is more effective to self learn what I need) +* The Ultimate Kubernetes Bootcamp; School of Devops; O'Reilly Online +* Algorithms Video Lectures; Robert Sedgewick; O'Reilly Online +* F5 Loadbalancers Training; 2-day on-site training; F5, Inc. ## Technical guides These are not whole books, but guides (smaller or larger) which I found very useful. in random order: * How CPUs work at https://cpu.land -* Raku Guide at https://raku.guide * Advanced Bash-Scripting Guide +* Raku Guide at https://raku.guide ## Podcasts @@ -177,58 +177,58 @@ These are not whole books, but guides (smaller or larger) which I found very use In random order: -* Fork Around And Find Out * The Pragmatic Engineer Podcast -* Wednesday Wisdom -* Cup o' Go [Golang] -* Modern Mentor -* The Changelog Podcast(s) -* Pratical AI +* Maintainable +* Fork Around And Find Out +* Dev Interrupted * BSD Now [BSD] +* Pratical AI +* Hidden Brain * The ProdCast (Google SRE Podcast) +* Modern Mentor +* The Changelog Podcast(s) +* Cup o' Go [Golang] +* Fallthrough [Golang] * Deep Questions with Cal Newport * Backend Banter -* Dev Interrupted -* Hidden Brain -* Fallthrough [Golang] -* Maintainable +* Wednesday Wisdom ### Podcasts I liked I liked them but am not listening to them anymore. The podcasts have either "finished" (no more episodes) or I stopped listening to them due to time constraints or a shift in my interests. -* Java Pub House -* Ship It (predecessor of Fork Around And Find Out) * FLOSS weekly * Go Time (predecessor of fallthrough) * Modern Mentor +* Java Pub House +* Ship It (predecessor of Fork Around And Find Out) * CRE: Chaosradio Express [german] ## Newsletters I like This is a mix of tech and non-tech newsletters I am subscribed to. In random order: -* Andreas Brandhorst Newsletter (Sci-Fi author) -* Golang Weekly -* The Imperfectionist * The Pragmatic Engineer -* Ruby Weekly -* Monospace Mentor -* byteSizeGo * The Valuable Dev +* Register Spill +* Andreas Brandhorst Newsletter (Sci-Fi author) +* Monospace Mentor +* Ruby Weekly +* The Imperfectionist +* Golang Weekly * Changelog News * VK Newsletter * Applied Go Weekly Newsletter -* Register Spill +* byteSizeGo ## Magazines I like(d) This is a mix of tech I like(d). I may not be a current subscriber, but now and then, I buy an issue. In random order: * LWN (online only) -* Linux Magazine -* freeX (not published anymore) * Linux User +* freeX (not published anymore) +* Linux Magazine # Formal education diff --git a/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md b/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md index 9faf878a..b62c4a2d 100644 --- a/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md +++ b/gemfeed/2025-12-07-f3s-kubernetes-with-freebsd-part-8.md @@ -59,7 +59,7 @@ Together, these form the "PLG" stack (Prometheus, Loki, Grafana), which is a pop All manifests for the f3s stack live in my configuration repository: -[codeberg.org/snonux/conf/f3s codeberg.org/snonux/conf/f3s](https:/codeberg.org/snonux/conf/src/branch/master/f3s) +[codeberg.org/snonux/conf/f3s ](https://codeberg.org/snonux/conf/src/branch/master/f3s) ## Persistent storage recap diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.md b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.md deleted file mode 100644 index 3ebdc823..00000000 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-8.md +++ /dev/null @@ -1,621 +0,0 @@ -# f3s: Kubernetes with FreeBSD - Part 8: Observability - -This is the 8th blog post about the f3s series for my self-hosting demands in a home lab. f3s? The "f" stands for FreeBSD, and the "3s" stands for k3s, the Kubernetes distribution I use on FreeBSD-based physical machines. - -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2025-04-05 f3s: Kubernetes with FreeBSD - Part 4: Rocky Linux Bhyve VMs](./2025-04-05-f3s-kubernetes-with-freebsd-part-4.md) -[2025-05-11 f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network](./2025-05-11-f3s-kubernetes-with-freebsd-part-5.md) -[2025-07-14 f3s: Kubernetes with FreeBSD - Part 6: Storage](./2025-07-14-f3s-kubernetes-with-freebsd-part-6.md) -[2025-10-02 f3s: Kubernetes with FreeBSD - Part 7: k3s and first pod deployments](./2025-10-02-f3s-kubernetes-with-freebsd-part-7.md) - -[](./f3s-kubernetes-with-freebsd-part-1/f3slogo.png) - -## Table of Contents - -* [⇢ f3s: Kubernetes with FreeBSD - Part 8: Observability](#f3s-kubernetes-with-freebsd---part-8-observability) -* [⇢ ⇢ Introduction](#introduction) -* [⇢ ⇢ Persistent storage recap](#persistent-storage-recap) -* [⇢ ⇢ The monitoring namespace](#the-monitoring-namespace) -* [⇢ ⇢ Installing Prometheus and Grafana](#installing-prometheus-and-grafana) -* [⇢ ⇢ ⇢ Prerequisites](#prerequisites) -* [⇢ ⇢ ⇢ Deploying with the Justfile](#deploying-with-the-justfile) -* [⇢ ⇢ ⇢ Exposing Grafana via ingress](#exposing-grafana-via-ingress) -* [⇢ ⇢ Installing Loki and Alloy](#installing-loki-and-alloy) -* [⇢ ⇢ ⇢ Prerequisites](#prerequisites) -* [⇢ ⇢ ⇢ Deploying Loki and Alloy](#deploying-loki-and-alloy) -* [⇢ ⇢ ⇢ Configuring Alloy](#configuring-alloy) -* [⇢ ⇢ ⇢ Adding Loki as a Grafana data source](#adding-loki-as-a-grafana-data-source) -* [⇢ ⇢ The complete monitoring stack](#the-complete-monitoring-stack) -* [⇢ ⇢ Using the observability stack](#using-the-observability-stack) -* [⇢ ⇢ ⇢ Viewing metrics in Grafana](#viewing-metrics-in-grafana) -* [⇢ ⇢ ⇢ Querying logs with LogQL](#querying-logs-with-logql) -* [⇢ ⇢ ⇢ Creating alerts](#creating-alerts) -* [⇢ ⇢ Monitoring external FreeBSD hosts](#monitoring-external-freebsd-hosts) -* [⇢ ⇢ ⇢ Installing Node Exporter on FreeBSD](#installing-node-exporter-on-freebsd) -* [⇢ ⇢ ⇢ Adding FreeBSD hosts to Prometheus](#adding-freebsd-hosts-to-prometheus) -* [⇢ ⇢ ⇢ FreeBSD memory metrics compatibility](#freebsd-memory-metrics-compatibility) -* [⇢ ⇢ ⇢ Disk I/O metrics limitation](#disk-io-metrics-limitation) -* [⇢ ⇢ Monitoring external OpenBSD hosts](#monitoring-external-openbsd-hosts) -* [⇢ ⇢ ⇢ Installing Node Exporter on OpenBSD](#installing-node-exporter-on-openbsd) -* [⇢ ⇢ ⇢ Adding OpenBSD hosts to Prometheus](#adding-openbsd-hosts-to-prometheus) -* [⇢ ⇢ ⇢ OpenBSD memory metrics compatibility](#openbsd-memory-metrics-compatibility) -* [⇢ ⇢ Summary](#summary) - -## Introduction - -In this blog post, I set up a complete observability stack for the k3s cluster. Observability is crucial for understanding what's happening inside the cluster—whether its tracking resource usage, debugging issues, or analysing application behaviour. The stack consists of four main components, all deployed into the `monitoring` namespace: - -* Prometheus: time-series database for metrics collection and alerting -* Grafana: visualisation and dashboarding frontend -* Loki: log aggregation system (like Prometheus, but for logs) -* Alloy: telemetry collector that ships logs from all pods to Loki - -Together, these form the "PLG" stack (Prometheus, Loki, Grafana), which is a popular open-source alternative to commercial observability platforms. - -All manifests for the f3s stack live in my configuration repository: - -[codeberg.org/snonux/conf/f3s codeberg.org/snonux/conf/f3s](https:/codeberg.org/snonux/conf/src/branch/master/f3s) - -## Persistent storage recap - -All observability components need persistent storage so that metrics and logs survive pod restarts. As covered in Part 6 of this series, the cluster uses NFS-backed persistent volumes: - -[f3s: Kubernetes with FreeBSD - Part 6: Storage](./2025-07-14-f3s-kubernetes-with-freebsd-part-6.md) - -The FreeBSD hosts (`f0`, `f1`, `f2`) serve as NFS servers, exporting ZFS datasets that are replicated across hosts using `zrepl`. The Rocky Linux k3s nodes (`r0`, `r1`, `r2`) mount these exports at `/data/nfs/k3svolumes`. This directory contains subdirectories for each application that needs persistent storage—including Prometheus, Grafana, and Loki. - -For example, the observability stack uses these paths on the NFS share: - -* `/data/nfs/k3svolumes/prometheus/data` — Prometheus time-series database -* `/data/nfs/k3svolumes/grafana/data` — Grafana configuration, dashboards, and plugins -* `/data/nfs/k3svolumes/loki/data` — Loki log chunks and index - -Each path gets a corresponding `PersistentVolume` and `PersistentVolumeClaim` in Kubernetes, allowing pods to mount them as regular volumes. Because the underlying storage is ZFS with replication, we get snapshots and redundancy for free. - -## The monitoring namespace - -First, I created the monitoring namespace where all observability components will live: - -```sh -$ kubectl create namespace monitoring -namespace/monitoring created -``` - -## Installing Prometheus and Grafana - -Prometheus and Grafana are deployed together using the `kube-prometheus-stack` Helm chart from the Prometheus community. This chart bundles Prometheus, Grafana, Alertmanager, and various exporters (Node Exporter, Kube State Metrics) into a single deployment. Ill explain what each component does in detail later when we look at the running pods. - -### Prerequisites - -Add the Prometheus Helm chart repository: - -```sh -$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts -$ helm repo update -``` - -Create the directories on the NFS server for persistent storage: - -```sh -[root@r0 ~]# mkdir -p /data/nfs/k3svolumes/prometheus/data -[root@r0 ~]# mkdir -p /data/nfs/k3svolumes/grafana/data -``` - -### Deploying with the Justfile - -The configuration repository contains a `Justfile` that automates the deployment. `just` is a handy command runner—think of it as a simpler, more modern alternative to `make`. I use it throughout the f3s repository to wrap repetitive Helm and kubectl commands: - -[just - A handy way to save and run project-specific commands](https://github.com/casey/just) -[codeberg.org/snonux/conf/f3s/prometheus](https://codeberg.org/snonux/conf/src/branch/master/f3s/prometheus) - -To install everything: - -```sh -$ cd conf/f3s/prometheus -$ just install -kubectl apply -f persistent-volumes.yaml -persistentvolume/prometheus-data-pv created -persistentvolume/grafana-data-pv created -persistentvolumeclaim/grafana-data-pvc created -helm install prometheus prometheus-community/kube-prometheus-stack \ - --namespace monitoring -f persistence-values.yaml -NAME: prometheus -LAST DEPLOYED: ... -NAMESPACE: monitoring -STATUS: deployed -``` - -The `persistence-values.yaml` configures Prometheus and Grafana to use the NFS-backed persistent volumes I mentioned earlier, ensuring data survives pod restarts. The persistent volume definitions bind to specific paths on the NFS share using `hostPath` volumes—the same pattern used for other services in Part 7: - -[f3s: Kubernetes with FreeBSD - Part 7: k3s and first pod deployments](./2025-10-02-f3s-kubernetes-with-freebsd-part-7.md) - -### Exposing Grafana via ingress - -The chart also deploys an ingress for Grafana, making it accessible at `grafana.f3s.foo.zone`. The ingress configuration follows the same pattern as other services in the cluster—Traefik handles the routing internally, while the OpenBSD edge relays terminate TLS and forward traffic through WireGuard. - -Once deployed, Grafana is accessible and comes pre-configured with Prometheus as a data source. You can verify the Prometheus service is running: - -```sh -$ kubectl get svc -n monitoring prometheus-kube-prometheus-prometheus -NAME TYPE CLUSTER-IP PORT(S) -prometheus-kube-prometheus-prometheus ClusterIP 10.43.152.163 9090/TCP,8080/TCP -``` - -Grafana connects to Prometheus using the internal service URL `http://prometheus-kube-prometheus-prometheus.monitoring.svc.cluster.local:9090`. The default Grafana credentials are `admin`/`prom-operator`, which should be changed immediately after first login. - -[](./f3s-kubernetes-with-freebsd-part-8/grafana-prometheus.png) - -[](./f3s-kubernetes-with-freebsd-part-8/grafana-dashboard.png) - -## Installing Loki and Alloy - -While Prometheus handles metrics, Loki handles logs. It's designed to be cost-effective and easy to operate—it doesn't index the contents of logs, only the metadata (labels), making it very efficient for storage. - -Alloy is Grafana's telemetry collector (the successor to Promtail). It runs as a DaemonSet on each node, tails container logs, and ships them to Loki. - -### Prerequisites - -Create the data directory on the NFS server: - -```sh -[root@r0 ~]# mkdir -p /data/nfs/k3svolumes/loki/data -``` - -### Deploying Loki and Alloy - -The Loki configuration also lives in the repository: - -[codeberg.org/snonux/conf/f3s/loki](https://codeberg.org/snonux/conf/src/branch/master/f3s/loki) - -To install: - -```sh -$ cd conf/f3s/loki -$ just install -helm repo add grafana https://grafana.github.io/helm-charts || true -helm repo update -kubectl apply -f persistent-volumes.yaml -persistentvolume/loki-data-pv created -persistentvolumeclaim/loki-data-pvc created -helm install loki grafana/loki --namespace monitoring -f values.yaml -NAME: loki -LAST DEPLOYED: ... -NAMESPACE: monitoring -STATUS: deployed -... -helm install alloy grafana/alloy --namespace monitoring -f alloy-values.yaml -NAME: alloy -LAST DEPLOYED: ... -NAMESPACE: monitoring -STATUS: deployed -``` - -Loki runs in single-binary mode with a single replica (`loki-0`), which is appropriate for a home lab cluster. This means there's only one Loki pod running at any time. If the node hosting Loki fails, Kubernetes will automatically reschedule the pod to another worker node—but there will be a brief downtime (typically under a minute) while this happens. For my home lab use case, this is perfectly acceptable. - -For full high-availability, you'd deploy Loki in microservices mode with separate read, write, and backend components, backed by object storage like S3 or MinIO instead of local filesystem storage. That's a more complex setup that I might explore in a future blog post—but for now, the single-binary mode with NFS-backed persistence strikes the right balance between simplicity and durability. - -### Configuring Alloy - -Alloy is configured via `alloy-values.yaml` to discover all pods in the cluster and forward their logs to Loki: - -```sh -discovery.kubernetes "pods" { - role = "pod" -} - -discovery.relabel "pods" { - targets = discovery.kubernetes.pods.targets - - rule { - source_labels = ["__meta_kubernetes_namespace"] - target_label = "namespace" - } - - rule { - source_labels = ["__meta_kubernetes_pod_name"] - target_label = "pod" - } - - rule { - source_labels = ["__meta_kubernetes_pod_container_name"] - target_label = "container" - } - - rule { - source_labels = ["__meta_kubernetes_pod_label_app"] - target_label = "app" - } -} - -loki.source.kubernetes "pods" { - targets = discovery.relabel.pods.output - forward_to = [loki.write.default.receiver] -} - -loki.write "default" { - endpoint { - url = "http://loki.monitoring.svc.cluster.local:3100/loki/api/v1/push" - } -} -``` - -This configuration automatically labels each log line with the namespace, pod name, container name, and app label, making it easy to filter logs in Grafana. - -### Adding Loki as a Grafana data source - -Loki doesn't have its own web UI—you query it through Grafana. First, verify the Loki service is running: - -```sh -$ kubectl get svc -n monitoring loki -NAME TYPE CLUSTER-IP PORT(S) -loki ClusterIP 10.43.64.60 3100/TCP,9095/TCP -``` - -To add Loki as a data source in Grafana: - -* Navigate to Configuration → Data Sources -* Click "Add data source" -* Select "Loki" -* Set the URL to: `http://loki.monitoring.svc.cluster.local:3100` -* Click "Save & Test" - -Once configured, you can explore logs in Grafana's "Explore" view. I'll show some example queries in the "Using the observability stack" section below. - -[](./f3s-kubernetes-with-freebsd-part-8/loki-explore.png) - -## The complete monitoring stack - -After deploying everything, here's what's running in the monitoring namespace: - -```sh -$ kubectl get pods -n monitoring -NAME READY STATUS RESTARTS AGE -alertmanager-prometheus-kube-prometheus-alertmanager-0 2/2 Running 0 42d -alloy-g5fgj 2/2 Running 0 29m -alloy-nfw8w 2/2 Running 0 29m -alloy-tg9vj 2/2 Running 0 29m -loki-0 2/2 Running 0 25m -prometheus-grafana-868f9dc7cf-lg2vl 3/3 Running 0 42d -prometheus-kube-prometheus-operator-8d7bbc48c-p4sf4 1/1 Running 0 42d -prometheus-kube-state-metrics-7c5fb9d798-hh2fx 1/1 Running 0 42d -prometheus-prometheus-kube-prometheus-prometheus-0 2/2 Running 0 42d -prometheus-prometheus-node-exporter-2nsg9 1/1 Running 0 42d -prometheus-prometheus-node-exporter-mqr25 1/1 Running 0 42d -prometheus-prometheus-node-exporter-wp4ds 1/1 Running 0 42d -``` - -And the services: - -```sh -$ kubectl get svc -n monitoring -NAME TYPE CLUSTER-IP PORT(S) -alertmanager-operated ClusterIP None 9093/TCP,9094/TCP -alloy ClusterIP 10.43.74.14 12345/TCP -loki ClusterIP 10.43.64.60 3100/TCP,9095/TCP -loki-headless ClusterIP None 3100/TCP -prometheus-grafana ClusterIP 10.43.46.82 80/TCP -prometheus-kube-prometheus-alertmanager ClusterIP 10.43.208.43 9093/TCP,8080/TCP -prometheus-kube-prometheus-operator ClusterIP 10.43.246.121 443/TCP -prometheus-kube-prometheus-prometheus ClusterIP 10.43.152.163 9090/TCP,8080/TCP -prometheus-kube-state-metrics ClusterIP 10.43.64.26 8080/TCP -prometheus-prometheus-node-exporter ClusterIP 10.43.127.242 9100/TCP -``` - -Let me break down what each pod does: - -* `alertmanager-prometheus-kube-prometheus-alertmanager-0`: the Alertmanager instance that receives alerts from Prometheus, deduplicates them, groups related alerts together, and routes notifications to the appropriate receivers (email, Slack, PagerDuty, etc.). It runs as a StatefulSet with persistent storage for silences and notification state. - -* `alloy-g5fgj, alloy-nfw8w, alloy-tg9vj`: three Alloy pods running as a DaemonSet, one on each k3s node. Each pod tails the container logs from its local node via the Kubernetes API and forwards them to Loki. This ensures log collection continues even if a node becomes isolated from the others. - -* `loki-0`: the single Loki instance running in single-binary mode. It receives log streams from Alloy, stores them in chunks on the NFS-backed persistent volume, and serves queries from Grafana. The `-0` suffix indicates it's a StatefulSet pod. - -* `prometheus-grafana-...`: the Grafana web interface for visualising metrics and logs. It comes pre-configured with Prometheus as a data source and includes dozens of dashboards for Kubernetes monitoring. Dashboards, users, and settings are persisted to the NFS share. - -* `prometheus-kube-prometheus-operator-...`: the Prometheus Operator that watches for custom resources (ServiceMonitor, PodMonitor, PrometheusRule) and automatically configures Prometheus to scrape new targets. This allows applications to declare their own monitoring requirements. - -* `prometheus-kube-state-metrics-...`: generates metrics about the state of Kubernetes objects themselves: how many pods are running, pending, or failed; deployment replica counts; node conditions; PVC status; and more. Essential for cluster-level dashboards. - -* `prometheus-prometheus-kube-prometheus-prometheus-0`: the Prometheus server that scrapes metrics from all configured targets (pods, services, nodes), stores them in a time-series database, evaluates alerting rules, and serves queries to Grafana. - -* `prometheus-prometheus-node-exporter-...`: three Node Exporter pods running as a DaemonSet, one on each node. They expose hardware and OS-level metrics: CPU usage, memory, disk I/O, filesystem usage, network statistics, and more. These feed the "Node Exporter" dashboards in Grafana. - -## Using the observability stack - -### Viewing metrics in Grafana - -The kube-prometheus-stack comes with many pre-built dashboards. Some useful ones include: - -* Kubernetes / Compute Resources / Cluster: overview of CPU and memory usage across the cluster -* Kubernetes / Compute Resources / Namespace (Pods): resource usage by namespace -* Node Exporter / Nodes: detailed host metrics like disk I/O, network, and CPU - -### Querying logs with LogQL - -In Grafana's Explore view, select Loki as the data source and try queries like: - -``` -# All logs from the services namespace -{namespace="services"} - -# Logs from pods matching a pattern -{pod=~"miniflux.*"} - -# Filter by log content -{namespace="services"} |= "error" - -# Parse JSON logs and filter -{namespace="services"} | json | level="error" -``` - -### Creating alerts - -Prometheus supports alerting rules that can notify you when something goes wrong. The kube-prometheus-stack includes many default alerts for common issues like high CPU usage, pod crashes, and node problems. These can be customised via PrometheusRule CRDs. - -## Monitoring external FreeBSD hosts - -The observability stack can also monitor servers outside the Kubernetes cluster. The FreeBSD hosts (`f0`, `f1`, `f2`) that serve NFS storage can be added to Prometheus using the Node Exporter. - -### Installing Node Exporter on FreeBSD - -On each FreeBSD host, install the node_exporter package: - -```sh -paul@f0:~ % doas pkg install -y node_exporter -``` - -Enable the service to start at boot: - -```sh -paul@f0:~ % doas sysrc node_exporter_enable=YES -node_exporter_enable: -> YES -``` - -Configure node_exporter to listen on the WireGuard interface. This ensures metrics are only accessible through the secure tunnel, not the public network. Replace the IP with the host's WireGuard address: - -```sh -paul@f0:~ % doas sysrc node_exporter_args='--web.listen-address=192.168.2.130:9100' -node_exporter_args: -> --web.listen-address=192.168.2.130:9100 -``` - -Start the service: - -```sh -paul@f0:~ % doas service node_exporter start -Starting node_exporter. -``` - -Verify it's running: - -```sh -paul@f0:~ % curl -s http://192.168.2.130:9100/metrics | head -3 -# HELP go_gc_duration_seconds A summary of the wall-time pause... -# TYPE go_gc_duration_seconds summary -go_gc_duration_seconds{quantile="0"} 0 -``` - -Repeat for the other FreeBSD hosts (`f1`, `f2`) with their respective WireGuard IPs. - -### Adding FreeBSD hosts to Prometheus - -Create a file `additional-scrape-configs.yaml` in the prometheus configuration directory: - -```yaml -- job_name: 'node-exporter' - static_configs: - - targets: - - '192.168.2.130:9100' # f0 via WireGuard - - '192.168.2.131:9100' # f1 via WireGuard - - '192.168.2.132:9100' # f2 via WireGuard - labels: - os: freebsd -``` - -The `job_name` must be `node-exporter` to match the existing dashboards. The `os: freebsd` label allows filtering these hosts separately if needed. - -Create a Kubernetes secret from this file: - -```sh -$ kubectl create secret generic additional-scrape-configs \ - --from-file=additional-scrape-configs.yaml \ - -n monitoring -``` - -Update `persistence-values.yaml` to reference the secret: - -```yaml -prometheus: - prometheusSpec: - additionalScrapeConfigsSecret: - enabled: true - name: additional-scrape-configs - key: additional-scrape-configs.yaml -``` - -Upgrade the Prometheus deployment: - -```sh -$ just upgrade -``` - -After a minute or so, the FreeBSD hosts appear in the Prometheus targets and in the Node Exporter dashboards in Grafana. - -[](./f3s-kubernetes-with-freebsd-part-8/grafana-freebsd-nodes.png) - -### FreeBSD memory metrics compatibility - -The default Node Exporter dashboards are designed for Linux and expect metrics like `node_memory_MemAvailable_bytes`. FreeBSD uses different metric names (`node_memory_size_bytes`, `node_memory_free_bytes`, etc.), so memory panels will show "No data" out of the box. - -To fix this, I created a PrometheusRule that generates synthetic Linux-compatible metrics from the FreeBSD equivalents: - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PrometheusRule -metadata: - name: freebsd-memory-rules - namespace: monitoring - labels: - release: prometheus -spec: - groups: - - name: freebsd-memory - rules: - - record: node_memory_MemTotal_bytes - expr: node_memory_size_bytes{os="freebsd"} - - record: node_memory_MemAvailable_bytes - expr: node_memory_free_bytes{os="freebsd"} + node_memory_inactive_bytes{os="freebsd"} + node_memory_cache_bytes{os="freebsd"} - - record: node_memory_MemFree_bytes - expr: node_memory_free_bytes{os="freebsd"} - - record: node_memory_Buffers_bytes - expr: node_memory_buffer_bytes{os="freebsd"} - - record: node_memory_Cached_bytes - expr: node_memory_cache_bytes{os="freebsd"} -``` - -This file is saved as `freebsd-recording-rules.yaml` and applied as part of the Prometheus installation. The `os="freebsd"` label (set in the scrape config) ensures these rules only apply to FreeBSD hosts. After applying, the memory panels in the Node Exporter dashboards populate correctly for FreeBSD. - -[freebsd-recording-rules.yaml on Codeberg](https://codeberg.org/snonux/conf/src/branch/master/f3s/prometheus/freebsd-recording-rules.yaml) - -### Disk I/O metrics limitation - -Unlike memory metrics, disk I/O metrics (`node_disk_read_bytes_total`, `node_disk_written_bytes_total`, etc.) are not available on FreeBSD. The Linux diskstats collector that provides these metrics doesn't have a FreeBSD equivalent in the node_exporter. - -The disk I/O panels in the Node Exporter dashboards will show "No data" for FreeBSD hosts. FreeBSD does expose ZFS-specific metrics (`node_zfs_arcstats_*`) for ARC cache performance, and per-dataset I/O stats are available via `sysctl kstat.zfs`, but mapping these to the Linux-style metrics the dashboards expect is non-trivial. Creating custom ZFS-specific dashboards is left as an exercise for another day. - -## Monitoring external OpenBSD hosts - -The same approach works for OpenBSD hosts. I have two OpenBSD edge relay servers (`blowfish`, `fishfinger`) that handle TLS termination and forward traffic through WireGuard to the cluster. These can also be monitored with Node Exporter. - -### Installing Node Exporter on OpenBSD - -On each OpenBSD host, install the node_exporter package: - -```sh -blowfish:~ $ doas pkg_add node_exporter -quirks-7.103 signed on 2025-10-13T22:55:16Z -The following new rcscripts were installed: /etc/rc.d/node_exporter -See rcctl(8) for details. -``` - -Enable the service to start at boot: - -```sh -blowfish:~ $ doas rcctl enable node_exporter -``` - -Configure node_exporter to listen on the WireGuard interface. This ensures metrics are only accessible through the secure tunnel, not the public network. Replace the IP with the host's WireGuard address: - -```sh -blowfish:~ $ doas rcctl set node_exporter flags '--web.listen-address=192.168.2.110:9100' -``` - -Start the service: - -```sh -blowfish:~ $ doas rcctl start node_exporter -node_exporter(ok) -``` - -Verify it's running: - -```sh -blowfish:~ $ curl -s http://192.168.2.110:9100/metrics | head -3 -# HELP go_gc_duration_seconds A summary of the wall-time pause... -# TYPE go_gc_duration_seconds summary -go_gc_duration_seconds{quantile="0"} 0 -``` - -Repeat for the other OpenBSD host (`fishfinger`) with its respective WireGuard IP (`192.168.2.111`). - -### Adding OpenBSD hosts to Prometheus - -Update `additional-scrape-configs.yaml` to include the OpenBSD targets: - -```yaml -- job_name: 'node-exporter' - static_configs: - - targets: - - '192.168.2.130:9100' # f0 via WireGuard - - '192.168.2.131:9100' # f1 via WireGuard - - '192.168.2.132:9100' # f2 via WireGuard - labels: - os: freebsd - - targets: - - '192.168.2.110:9100' # blowfish via WireGuard - - '192.168.2.111:9100' # fishfinger via WireGuard - labels: - os: openbsd -``` - -The `os: openbsd` label allows filtering these hosts separately from FreeBSD and Linux nodes. - -### OpenBSD memory metrics compatibility - -OpenBSD uses the same memory metric names as FreeBSD (`node_memory_size_bytes`, `node_memory_free_bytes`, etc.), so a similar PrometheusRule is needed to generate Linux-compatible metrics: - -```yaml -apiVersion: monitoring.coreos.com/v1 -kind: PrometheusRule -metadata: - name: openbsd-memory-rules - namespace: monitoring - labels: - release: prometheus -spec: - groups: - - name: openbsd-memory - rules: - - record: node_memory_MemTotal_bytes - expr: node_memory_size_bytes{os="openbsd"} - labels: - os: openbsd - - record: node_memory_MemAvailable_bytes - expr: node_memory_free_bytes{os="openbsd"} + node_memory_inactive_bytes{os="openbsd"} + node_memory_cache_bytes{os="openbsd"} - labels: - os: openbsd - - record: node_memory_MemFree_bytes - expr: node_memory_free_bytes{os="openbsd"} - labels: - os: openbsd - - record: node_memory_Cached_bytes - expr: node_memory_cache_bytes{os="openbsd"} - labels: - os: openbsd -``` - -This file is saved as `openbsd-recording-rules.yaml` and applied alongside the FreeBSD rules. Note that OpenBSD doesn't expose a buffer memory metric, so that rule is omitted. - -[openbsd-recording-rules.yaml on Codeberg](https://codeberg.org/snonux/conf/src/branch/master/f3s/prometheus/openbsd-recording-rules.yaml) - -After running `just upgrade`, the OpenBSD hosts appear in Prometheus targets and the Node Exporter dashboards. - -## Summary - -With Prometheus, Grafana, Loki, and Alloy deployed, I now have complete visibility into the k3s cluster, the FreeBSD storage servers, and the OpenBSD edge relays: - -* metrics: Prometheus collects and stores time-series data from all components -* Logs: Loki aggregates logs from all containers, searchable via Grafana -* Visualisation: Grafana provides dashboards and exploration tools -* Alerting: Alertmanager can notify on conditions defined in Prometheus rules - -This observability stack runs entirely on the home lab infrastructure, with data persisted to the NFS share. It's lightweight enough for a three-node cluster but provides the same capabilities as production-grade setups. - -Other *BSD-related posts: - -[2025-10-02 f3s: Kubernetes with FreeBSD - Part 7: k3s and first pod deployments](./2025-10-02-f3s-kubernetes-with-freebsd-part-7.md) -[2025-07-14 f3s: Kubernetes with FreeBSD - Part 6: Storage](./2025-07-14-f3s-kubernetes-with-freebsd-part-6.md) -[2025-05-11 f3s: Kubernetes with FreeBSD - Part 5: WireGuard mesh network](./2025-05-11-f3s-kubernetes-with-freebsd-part-5.md) -[2025-04-05 f3s: Kubernetes with FreeBSD - Part 4: Rocky Linux Bhyve VMs](./2025-04-05-f3s-kubernetes-with-freebsd-part-4.md) -[2025-02-01 f3s: Kubernetes with FreeBSD - Part 3: Protecting from power cuts](./2025-02-01-f3s-kubernetes-with-freebsd-part-3.md) -[2024-12-03 f3s: Kubernetes with FreeBSD - Part 2: Hardware and base installation](./2024-12-03-f3s-kubernetes-with-freebsd-part-2.md) -[2024-11-17 f3s: Kubernetes with FreeBSD - Part 1: Setting the stage](./2024-11-17-f3s-kubernetes-with-freebsd-part-1.md) -[2024-04-01 KISS high-availability with OpenBSD](./2024-04-01-KISS-high-availability-with-OpenBSD.md) -[2024-01-13 One reason why I love OpenBSD](./2024-01-13-one-reason-why-i-love-openbsd.md) -[2022-10-30 Installing DTail on OpenBSD](./2022-10-30-installing-dtail-on-openbsd.md) -[2022-07-30 Let's Encrypt with OpenBSD and Rex](./2022-07-30-lets-encrypt-with-openbsd-and-rex.md) -[2016-04-09 Jails and ZFS with Puppet on FreeBSD](./2016-04-09-jails-and-zfs-on-freebsd-with-puppet.md) - -E-Mail your comments to `paul@nospam.buetow.org` - -[Back to the main site](../) @@ -1,6 +1,6 @@ # Hello! -> This site was generated at 2025-12-06T23:58:24+02:00 by `Gemtexter` +> This site was generated at 2025-12-07T00:32:01+02:00 by `Gemtexter` Welcome to the foo.zone! diff --git a/uptime-stats.md b/uptime-stats.md index d6be3822..241a2f30 100644 --- a/uptime-stats.md +++ b/uptime-stats.md @@ -1,6 +1,6 @@ # My machine uptime stats -> This site was last updated at 2025-12-06T23:58:24+02:00 +> This site was last updated at 2025-12-07T00:32:01+02:00 The following stats were collected via `uptimed` on all of my personal computers over many years and the output was generated by `guprecords`, the global uptime records stats analyser of mine. @@ -53,7 +53,7 @@ Uptime is the total uptime of a host over the entire lifespan. | Pos | Host | Uptime | Last Kernel | +-----+----------------+-----------------------------+-----------------------------------+ | 1. | vulcan | 4 years, 5 months, 6 days | Linux 3.10.0-1160.81.1.el7.x86_64 | -| 2. | *earth | 3 years, 11 months, 12 days | Linux 6.17.8-300.fc43.x86_64 | +| 2. | *earth | 3 years, 11 months, 15 days | Linux 6.17.8-300.fc43.x86_64 | | 3. | *blowfish | 3 years, 10 months, 2 days | OpenBSD 7.7 | | 4. | sun | 3 years, 9 months, 26 days | FreeBSD 10.3-RELEASE-p24 | | 5. | uranus | 3 years, 9 months, 5 days | NetBSD 10.1 | @@ -65,7 +65,7 @@ Uptime is the total uptime of a host over the entire lifespan. | 11. | mega15289 | 1 years, 12 months, 17 days | Darwin 23.4.0 | | 12. | tauceti-f | 1 years, 9 months, 18 days | Linux 3.2.0-3-amd64 | | 13. | t450 | 1 years, 7 months, 26 days | FreeBSD 14.2-RELEASE | -| 14. | *mega-m3-pro | 1 years, 6 months, 14 days | Darwin 24.6.0 | +| 14. | *mega-m3-pro | 1 years, 6 months, 20 days | Darwin 24.6.0 | | 15. | mega8477 | 1 years, 3 months, 25 days | Darwin 13.4.0 | | 16. | host0 | 1 years, 3 months, 9 days | FreeBSD 6.2-RELEASE-p5 | | 17. | *makemake | 1 years, 3 months, 7 days | Linux 6.9.9-200.fc40.x86_64 | @@ -85,7 +85,7 @@ Score is calculated by combining all other metrics. +-----+----------------+-------+-----------------------------------+ | 1. | uranus | 340 | NetBSD 10.1 | | 2. | vulcan | 275 | Linux 3.10.0-1160.81.1.el7.x86_64 | -| 3. | *earth | 271 | Linux 6.17.8-300.fc43.x86_64 | +| 3. | *earth | 272 | Linux 6.17.8-300.fc43.x86_64 | | 4. | *blowfish | 243 | OpenBSD 7.7 | | 5. | sun | 238 | FreeBSD 10.3-RELEASE-p24 | | 6. | uugrn | 211 | FreeBSD 11.2-RELEASE-p4 | @@ -99,7 +99,7 @@ Score is calculated by combining all other metrics. | 14. | *makemake | 139 | Linux 6.9.9-200.fc40.x86_64 | | 15. | t450 | 119 | FreeBSD 14.2-RELEASE | | 16. | tauceti-f | 108 | Linux 3.2.0-3-amd64 | -| 17. | *mega-m3-pro | 98 | Darwin 24.6.0 | +| 17. | *mega-m3-pro | 99 | Darwin 24.6.0 | | 18. | tauceti-e | 96 | Linux 3.2.0-4-amd64 | | 19. | callisto | 86 | Linux 4.0.4-303.fc22.x86_64 | | 20. | mega8477 | 80 | Darwin 13.4.0 | @@ -149,7 +149,7 @@ Lifespan is the total uptime + the total downtime of a host. | 2. | dionysus | 8 years, 6 months, 17 days | FreeBSD 13.0-RELEASE-p11 | | 3. | alphacentauri | 6 years, 9 months, 13 days | FreeBSD 11.4-RELEASE-p7 | | 4. | *makemake | 4 years, 10 months, 16 days | Linux 6.9.9-200.fc40.x86_64 | -| 5. | *earth | 4 years, 5 months, 11 days | Linux 6.17.8-300.fc43.x86_64 | +| 5. | *earth | 4 years, 5 months, 14 days | Linux 6.17.8-300.fc43.x86_64 | | 6. | vulcan | 4 years, 5 months, 6 days | Linux 3.10.0-1160.81.1.el7.x86_64 | | 7. | *blowfish | 3 years, 10 months, 3 days | OpenBSD 7.7 | | 8. | sun | 3 years, 10 months, 2 days | FreeBSD 10.3-RELEASE-p24 | @@ -211,7 +211,7 @@ Uptime is the total uptime of a host over the entire lifespan. | 2. | *OpenBSD 7... | 7 years, 6 months, 29 days | | 3. | FreeBSD 10... | 5 years, 9 months, 9 days | | 4. | Linux 5... | 4 years, 10 months, 21 days | -| 5. | *Linux 6... | 3 years, 2 months, 10 days | +| 5. | *Linux 6... | 3 years, 2 months, 13 days | | 6. | Linux 4... | 2 years, 7 months, 22 days | | 7. | FreeBSD 11... | 2 years, 4 months, 28 days | | 8. | *FreeBSD 14... | 2 years, 3 months, 24 days | @@ -219,7 +219,7 @@ Uptime is the total uptime of a host over the entire lifespan. | 10. | Darwin 13... | 1 years, 3 months, 25 days | | 11. | FreeBSD 6... | 1 years, 3 months, 9 days | | 12. | Darwin 23... | 0 years, 11 months, 7 days | -| 13. | *Darwin 24... | 0 years, 10 months, 17 days | +| 13. | *Darwin 24... | 0 years, 10 months, 23 days | | 14. | OpenBSD 4... | 0 years, 8 months, 12 days | | 15. | Darwin 21... | 0 years, 8 months, 2 days | | 16. | Darwin 18... | 0 years, 7 months, 5 days | @@ -250,14 +250,14 @@ Score is calculated by combining all other metrics. | 10. | Darwin 13... | 80 | | 11. | FreeBSD 6... | 75 | | 12. | Darwin 23... | 56 | -| 13. | *Darwin 24... | 54 | +| 13. | *Darwin 24... | 55 | | 14. | OpenBSD 4... | 39 | | 15. | Darwin 21... | 38 | | 16. | Darwin 18... | 32 | | 17. | Darwin 22... | 30 | | 18. | Darwin 15... | 29 | -| 19. | FreeBSD 5... | 25 | -| 20. | FreeBSD 13... | 25 | +| 19. | FreeBSD 13... | 25 | +| 20. | FreeBSD 5... | 25 | +-----+----------------+-------+ ``` @@ -285,10 +285,10 @@ Uptime is the total uptime of a host over the entire lifespan. +-----+------------+-----------------------------+ | Pos | KernelName | Uptime | +-----+------------+-----------------------------+ -| 1. | *Linux | 28 years, 3 months, 5 days | +| 1. | *Linux | 28 years, 3 months, 8 days | | 2. | *FreeBSD | 12 years, 2 months, 24 days | | 3. | *OpenBSD | 8 years, 2 months, 7 days | -| 4. | *Darwin | 5 years, 2 months, 2 days | +| 4. | *Darwin | 5 years, 2 months, 8 days | | 5. | NetBSD | 0 years, 1 months, 1 days | +-----+------------+-----------------------------+ ``` @@ -304,7 +304,7 @@ Score is calculated by combining all other metrics. | 1. | *Linux | 1875 | | 2. | *FreeBSD | 862 | | 3. | *OpenBSD | 523 | -| 4. | *Darwin | 337 | +| 4. | *Darwin | 338 | | 5. | NetBSD | 0 | +-----+------------+-------+ ``` |