node_exporter
net-test
Our great sponsors
node_exporter | net-test | |
---|---|---|
78 | 1 | |
10,132 | 39 | |
2.7% | - | |
8.9 | 0.0 | |
3 days ago | over 2 years ago | |
Go | Go | |
Apache License 2.0 | MIT License |
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.
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
-
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?
-
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.
-
multi line regex help
A good example of hwmon parsing can be found in hwmon_linux.go.
-
Does anyone know of a guide for installing snmp_exporter on ASUS router running merlin firmware?
The only issue is ASUS has weird kernel patches and you will need to use --no-collector.netdev.netlink to work around them.
-
Monitoring Linux instances with Prometheus and Grafana
$ wget https://github.com/prometheus/node_exporter/releases/download/v1.0.1/node_exporter-1.0.1.linux-amd64.tar.gz Uncompress and rename the folder $ tar xvf node_exporter-1.0.1.linux-amd64.tar.gz $ mv node_exporter-1.0.1.linux-amd64 ne_files
-
My Rust journey and how to learn Rust
Since I have a specific problem that needs to be solved, I need to implement a node_exporter to complete the transformation of the monitoring stack. So I learned Rust through the learning-by-doing mode.
-
AWS EC2 Auto Scaling, Target Tracking Policies and Prometheus Exporters
#!/bin/bash yum update -y # Install CWA yum install amazon-cloudwatch-agent -y # Install Nginx and configure the stub status module amazon-linux-extras install nginx1.12 -y aws ssm get-parameter --name {{ nginx_stub_status_config_parameter_path }} --region {{ region }} --output text --query Parameter.Value > {{ nginx_config_file_path }} # Add a user to run the exporters useradd --no-create-home metrics_exporter # Install Node Exporter wget https://github.com/prometheus/node_exporter/releases/download/v1.4.0/node_exporter-1.4.0.linux-amd64.tar.gz tar xzf node_exporter-1.4.0.linux-amd64.tar.gz cp node_exporter-1.4.0.linux-amd64/node_exporter /usr/local/bin/node_exporter rm -rf node_exporter-1.4.0.linux-amd64.tar.gz node_exporter-1.4.0.linux-amd64 # Create Node Exporter systemd service cat << 'EOF' > /etc/systemd/system/node-exporter.service [Unit] Description=Prometheus Node Exporter Service After=network.target [Service] User=metrics_exporter Group=metrics_exporter Type=simple ExecStart=/usr/local/bin/node_exporter [Install] WantedBy=multi-user.target EOF # Install Nginx Exporter wget https://github.com/nginxinc/nginx-prometheus-exporter/releases/download/v0.11.0/nginx-prometheus-exporter_0.11.0_linux_amd64.tar.gz tar xzf nginx-prometheus-exporter_0.11.0_linux_amd64.tar.gz cp nginx-prometheus-exporter /usr/local/bin/nginx-prometheus-exporter rm -rf nginx-prometheus-exporter_0.11.0_linux_amd64.tar.gz nginx-prometheus-exporter # Create Nginx Exporter systemd service cat << 'EOF' > /etc/systemd/system/nginx-prometheus-exporter.service [Unit] Description=Prometheus Nginx Exporter Service After=network.target [Service] User=metrics_exporter Group=metrics_exporter Type=simple ExecStart=/usr/local/bin/nginx-prometheus-exporter -nginx.scrape-uri http://127.0.0.1:{{ nginx_stub_status_port }}/metrics -web.listen-address=127.0.0.1:9113 [Install] WantedBy=multi-user.target EOF # Configure CWA aws ssm get-parameter --name {{ cwa_prometheus_parameter_path }} --region {{ region }} --with-decryption --output text --query Parameter.Value > /opt/aws/amazon-cloudwatch-agent/etc/prometheus.yml /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -c ssm:"{{ cwa_settings_parameter_path }}" -s # Start everything up systemctl daemon-reload systemctl enable nginx systemctl start nginx systemctl enable node-exporter systemctl start node-exporter systemctl enable nginx-prometheus-exporter systemctl start nginx-prometheus-exporter
net-test
-
Internet-monitoring – A Docker Stack which Monitors your home network
Cool! It's so funny I just recently took an old bash script of mine which did something similar and have been upgrading it into a proper application which exports metrics to Prometheus and Grafana: https://github.com/Noah-Huppert/net-test
I saw a comment below where some was rolling their eyes that you "complicated" stuff with Prometheus, Grafana, and Docker and how you could just use Bash scripts and crons. As I just upgraded my codebase from this more bare metal approach to this "more complex setup" I'd like to mention: there's no way you could do time series statistical analysis easily with "just a cron job and a bash script". Prometheus and Grafana are for more than just buzz words. Prometheus offers an advanced time series database which allows you to, at minimum, do more robust analysis using data techniques like Histograms. As for Grafana, it makes exploring data dead easy. Providing users with a Docker Compose setup is also something I did with my tool and the benefits are huge. It lets me distribute a setup which relies on multiple moving parts working smoothly together. Sure I could write a whole wiki on how you should setup Prometheus Grafana and my tool, or I could distribute the setup with a configuration as code tool. Ensuring that even if someone doesn't want to use Docker Compose they can at least read my configuration as code and see exactly what I did to setup my tool.
What are some alternatives?
cadvisor - Analyzes resource usage and performance characteristics of running containers.
process-exporter - Prometheus exporter that mines /proc to report on selected processes
Netdata - Monitor your servers, containers, and applications, in high-resolution and in real-time.
ping_exporter - Prometheus exporter for ICMP echo requests using https://github.com/digineo/go-ping
fortigate_exporter - Prometheus exporter for Fortigate firewalls
windows_exporter - Prometheus exporter for Windows machines
prometheus - The Prometheus monitoring system and time series database.
node-exporter-textfile-collector-scripts - Scripts for node-exporter's textfile collector
yet-another-cloudwatch-exporter - Prometheus exporter for AWS CloudWatch - Discovers services through AWS tags, gets CloudWatch metrics data and provides them as Prometheus metrics with AWS tags as labels
filestat_exporter - Prometheus exporter gathering metrics about file size, modification time and other stats
Telegraf - The plugin-driven server agent for collecting & reporting metrics.