Quick Start: Installing and Configuring FG Ping in 10 Minutes
FG Ping is a lightweight, reliable tool for active network monitoring and latency measurement. This quick-start guide walks you through installing FG Ping, performing an initial configuration, and running your first tests — all in about 10 minutes.
What you’ll need (assumed defaults)
- A machine running Linux (Ubuntu/Debian) or macOS (instructions below).
- sudo/local admin access.
- Basic familiarity with terminal/SSH.
- Network target(s) to test (IP or hostname).
1. Install FG Ping (2–4 minutes)
On Debian/Ubuntu
bash
sudo apt update sudo apt install -y fg-ping
On macOS (Homebrew)
bash
brew update brew install fg-ping
If a packaged version isn’t available, install from source:
bash
git clone https://example.com/fg-ping.git cd fg-ping sudo ./install.sh
2. Verify installation (30 seconds)
bash
fg-ping –version
Expected: a version string (e.g., fg-ping 1.2.0). If you see an error, confirm PATH and reinstall.
3. Basic usage — single target (1 minute)
Ping a host once per second, 10 times:
bash
fg-ping -c 10 -i 1 example.com
Key flags:
- -c N : count (number of pings)
- -i S : interval in seconds
4. Common useful options (1 minute)
- Continuous with timestamped output:
bash
fg-ping -i 1 –timestamps example.com
- Set packet size:
bash
fg-ping -s 128 example.com
- Use ICMP or UDP mode (if supported):
bash
fg-ping –mode udp example.com
5. Configure a profile for repeated tests (2 minutes)
Create a simple config file at ~/.fg-ping/config.yaml:
yaml
default: interval: 1 count: 0 # 0 = continuous timeout: 5 mode: icmp targets: - name: prod-web host: web.example.com - name: dns-1 host: 8.8.8.8
Start with:
bash
fg-ping –profile default
6. Run tests and collect results (1 minute)
Run a named target from the config:
bash
fg-ping –target prod-web –output csv > prod-web-$(date +%s).csv
Options:
- –output csv/json : export results for analysis
- –target NAME : use target from config
7. Basic troubleshooting (30 seconds)
- Permission denied for ICMP: run with sudo or use UDP mode.
- No command found: confirm install path and that fg-ping is in PATH.
- Unexpected high latency: test from another host to isolate network vs. target issues.
8. Next steps (optional)
- Schedule fg-ping via cron/systemd timer for continuous monitoring.
- Integrate CSV/JSON output into dashboards (Grafana/Prometheus) via a collector script.
- Explore advanced flags: jitter, packet loss thresholds, alerting hooks.
Leave a Reply