-
-
Notifications
You must be signed in to change notification settings - Fork 19
Features Smokeping
DOCSight can display live latency graphs from your Smokeping instance, giving you network latency and packet loss data alongside your DOCSIS signal metrics.
Smokeping continuously pings configured network targets and visualizes the results as graphs showing latency distribution, jitter, and packet loss over time. Combined with DOCSight's DOCSIS monitoring, you can see whether latency spikes correlate with signal degradation or are caused by something further upstream.
- Install and configure Smokeping on your network (e.g., as a Docker container)
- Note the base URL of your Smokeping web interface (e.g.,
http://192.168.178.15:8067/smokeping) - In DOCSight Settings, expand Smokeping
- Enter the Smokeping URL and your target names (comma-separated)
- Save
Target names must match the hierarchy in your Smokeping configuration. For example, a target at Global > Google becomes Global.Google.
The guided setup dialog links directly to the Smokeping module settings panel and explains the base URL, target naming, and validation path. DOCSight shows the graphs after the settings are saved and refreshed, if the configured Smokeping instance is reachable.
Smokeping is disabled by default on new installs. Enable the module in Settings, then configure the Smokeping base URL and target list there. The current release stores these as module configuration values in config.json; SMOKEPING_URL and SMOKEPING_TARGETS are not environment variables.
| Config key | Description |
|---|---|
smokeping_url |
Base URL of your Smokeping instance (without /cache/) |
smokeping_targets |
Comma-separated list of targets (e.g., Global.Google, Vodafone.Hop2) |
The Smokeping section in the sidebar shows live graphs for all configured targets with four timespan tabs:
| Timespan | What it shows |
|---|---|
| 3h | Last 3 hours -- detailed, per-ping view |
| 30h | Last 30 hours -- shows diurnal patterns |
| 10d | Last 10 days -- weekly trends |
| 1y | Last year -- seasonal overview |
| Smokeping | BQM | |
|---|---|---|
| Data source | Your own Smokeping instance | ThinkBroadband's servers |
| Storage | No local storage, proxied live | Daily PNG snapshots stored in DB |
| Refresh | Real-time with 60s cache | Once per day |
| Targets | Configurable (any host) | Fixed (your ThinkBroadband line) |
| Latency detail | Per-ping distribution | Aggregated min/avg/max bands |
Use Smokeping when you want real-time latency monitoring to specific endpoints. Use BQM when you want a daily quality overview from an external perspective.
Unlike BQM (which stores daily snapshots), Smokeping uses a proxy approach:
- DOCSight proxies graph requests directly to your Smokeping instance's CGI
- Each graph load triggers Smokeping to regenerate its cache with fresh data
- A short cache (60 seconds) prevents excessive requests when switching views
- No database storage needed, graphs are always current
Home | Quick Start | Configuration | API Reference | GitHub
- Quick Start
- Installation
- Running without Docker
- Podman Quadlet
- Configuration
- Reverse Proxy
- Example Compose Stacks
- Dashboard
- Connection Monitor
- Signal Trends
- Before/After Comparison
- Channel Timeline & Compare
- Event Log
- Smart Capture
- Gaming Quality Index
- Modulation Performance
- Cable Segment Utilization
- In-App Glossary
- Speedtest Tracker
- BNetzA Breitbandmessung
- ThinkBroadband BQM
- Smokeping
- Weather
- Netzbremse (Peering)
- Notifications
- Home Assistant (MQTT)
- Prometheus Metrics