HomeLab
node_exporter
HomeLab | node_exporter | |
---|---|---|
30 | 78 | |
209 | 10,315 | |
- | 1.8% | |
9.9 | 8.9 | |
1 day ago | 2 days ago | |
Python | Go | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
HomeLab
- Some Kubernetes stuff testing
-
Do I need Kubernetes?
And if you are interested how I've done it: https://github.com/Michaelpalacce/HomeLab
-
How do you automate the setup of file-less config applications (eg. Uptime Kuma)?
Example of a service that is being backed up (see backup.velero.io/backup-volume): https://github.com/Michaelpalacce/HomeLab/blob/master/Helm/apps/uptimekuma/templates/deployment.yaml
-
I'm a noob at homelab stuff, have three spare rack mount PC's to build something out of. What services are you hosting?
But for me https://github.com/Michaelpalacce/HomeLab/tree/master/cluster/homelab/apps
- K3S With ContainerD Grafana Dashboard And Dashy HomePage
-
Has anyone used BotKube?
So I've been trying to get botkube to work, but it seems to me like the helm chart documentation is outdated? I've been looking at the values and trying to make things work and it didn't really work for me.. https://github.com/Michaelpalacce/HomeLab/blob/master/cluster/homelab/apps/botkube/helmrelease.yaml is what I tried
- What do you have running on your Homeserver?
-
Looking for some thoughts on backup solutions for Kubernetes
And here is some documentation and specifics I've ran into. https://github.com/Michaelpalacce/HomeLab/blob/master/docs/Backups.md
-
How to orchestrate all services on server?
Also for configuration storage and git, I recommend taking a gitops approach to things. You can checkup FluxCD2. Here is my repo for reference https://github.com/Michaelpalacce/HomeLab
-
Looking for tips / recommendations for new selfhoster
A few suggestions and thinks I wish I knew when I started ( personal opinions incoming ): 1. Get a single well sized server ( I'd go for 8 cpus .. And like more than 16 gigs of ram and 250+ ssd, ideally m.2 nvme ). Don't bother with raspberry pis.. Check my profile for my previous post to see a comparison of raspberry pi cluster and a x86 cluster... 2. Install proxmox to do virtualization 3. The majority of People in this sub hate kubernetes and the minority is scared to speak, but install k3s on the vms you spin up, this way you can scale resources and not worry about some elaborate setup of which containers go to which node and how to setup tls offloading, load balancing and much much much more as kubernetes will handle it for you. ( bonus since you are a devops engineer so you are probably used to kube clusters ) 4. Use Velero to do restic backups to s3 for services that are critical like dbs and password managers etc. 5. Do everything with ansible or GitOps! My personal homelab is here: https://github.com/Michaelpalacce/HomeLab utilizing ansible, flux for GitOps and renovate to keep my services up to date ( note to say my cluster spin up isn't as nice as I want it to be since when provisioning I have a Dependency on some secrets which I do manually.. But this is only first cluster setup ) 6. Setup a VPN and administrative services on the raspberry pi you have lying around. Personally my VPN is on the router but if yours doesn't support it, do that. 7. After you are done setting everything up and you have a backup, format the drives and reinstall the vms and re set everything up. Document the process, write automation scripts until satisfied... I genuinely recommend you do this like 3 times...... 8. Vpn I guess a lot of people like wireguard or adguard home... Doesn't really matter as long as it's not open vpn and it supports multiple threads. 9. Setup nodered for some automation around your new home, you'll love it. 10. Firefly is amazing! 11. Make sure that your CSI ( Container storage interface ) supports replication. Keep 3 replicas of critical volumes! 11. If you need any help, don't forget to ask :) personally shoot me a dm and I'll do my best to help, but I'm sure most of us here would
node_exporter
-
Prometheus Fundamentals (Lesson-01)
$ wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz $ tar -xzvf node_exporter-1.7.0.linux-amd64.tar.gz
-
List of your reverse proxied services
Node Exporter
-
Best way to monitor disk space, RAM in remote servers and get alerts when full?
The Prometheus node_exporter can provide this information, doesn't require root. You could run it as a systemd user unit if you don't have root.
-
Best Course/Learning Path for mastering Prometheus and Grafana
I personally find it best to learn through experimentation. Start with reading a bit about Prometheus and Grafana through their docs, and then familiarise yourself with setting up a local Prometheus + Grafana instance either locally or with docker using docker-compose, along with something to generate /metrics endpoint for Prometheus to scrape from such as a custom Prometheus exporter in Python or using Node Exporter.
-
Linux Traffic Monitoring
Your best bet might be to fork node_exporter to get you more verbose socket stats: https://github.com/prometheus/node_exporter/blob/master/collector/sockstat_linux.go
-
Tool to monitor disk space
I use Grafana + Prometheus + Node Exporter.
- Is there a dashboard of sorts that can keep track of my linux-based computers and VMs to that I can easily see if any of them have updates or are running low on storage and et cetera?
-
Would SNMP present less of a load than SSH to get interface metrics from older cisco 3K series switches?
Crazy idea, can't NX devices run Docker? I wonder if the node_exporter would work.
-
Questions about Kubernetes
Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.
-
How to log system usage: RAM, CPU, over a long time to detect which component is slowing down?
You may setup node exporter and collect metrics with prometheus for example. Its not quite "simple" way, but still you may find it useful.
What are some alternatives?
changedetection.io - The best and simplest free open source web page change detection, website watcher, restock monitor and notification service. Restock Monitor, change detection. Designed for simplicity - Simply monitor which websites had a text change for free. Free Open source web page change detection, Website defacement monitoring, Price change notification
cadvisor - Analyzes resource usage and performance characteristics of running containers.
charts - ⚠️ Deprecated : Helm charts for applications you run at home
process-exporter - Prometheus exporter that mines /proc to report on selected processes
draw.io - draw.io is a JavaScript, client-side editor for general diagramming.
Netdata - The open-source observability platform everyone needs
docker-traefik - Docker media and home server stack with Docker Compose, Traefik, Swarm Mode, Google OAuth2/Authelia, and LetsEncrypt
ping_exporter - Prometheus exporter for ICMP echo requests using https://github.com/digineo/go-ping
dashboard-icons - 🚚 Dashboard Icons has moved to another home!
fortigate_exporter - Prometheus exporter for Fortigate firewalls
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
windows_exporter - Prometheus exporter for Windows machines