docs: Add monitoring migration architecture document#3
docs: Add monitoring migration architecture document#3ProjectInitiative wants to merge 1 commit intomainfrom
Conversation
Create an architecture decision record detailing the migration from a decentralized Python health-reporter script to a centralized Prometheus and Loki stack hosted on Kubernetes. This document outlines: - The target architecture for K8s nodes (capstans/lightships) and the non-K8s node (cargohold). - Integration of existing NixOS exporters with the K8s stack. - Specific alerting rules for node down, filesystem read-only, and drive failures. - A step-by-step migration plan. Co-authored-by: ProjectInitiative <6314611+ProjectInitiative@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This PR introduces an architecture document
docs/architecture/decisions/0001-monitoring-migration.mdto guide the migration of the monitoring system.What:
health-reporterscript with akube-prometheus-stack+Lokisolution.cargoholdNAS (non-K8s) from the K8s cluster.Why:
Verification:
PR created automatically by Jules for task 17251902889312121519 started by @ProjectInitiative