Reading the WarDragon Analytics map and dashboards
Once kits are reporting to WarDragon Analytics, there are two places to look: the web map for what is happening now, and the dashboards for history and patterns across kits. This article covers what each view shows.
The web map
Open port 8090 on the Analytics server. The map shows drone tracks from every connected kit with their trails, plus pilot and home markers where the aircraft provides them, refreshing every five seconds. The same interface holds the Kit Manager for adding kits and CSV export for reporting.
The dashboards
Open port 3000 on the Analytics server. The default login is shown in the output when Analytics is first started. Four dashboards are prebuilt:
| Dashboard | What it shows |
|---|---|
| Tactical Overview | Active drone count, a status grid for every kit, kit health (processor, memory, disk, temperature), a detection timeline, the manufacturers seen most often, and an alert summary. |
| Pattern Analysis | Drones seen repeatedly, the same operator associated with more than one drone, drones active together in the same window, and frequencies used repeatedly. |
| Multi-Kit Correlation | Drones seen by more than one kit, coverage by kit, a detection density heatmap, and tracks passing from one kit’s coverage to another’s. |
| Anomaly Detection | Rapid climbs or descents, unusual speeds, signal strength changes, and other behavior outside a track’s usual pattern. |
Note Pattern and anomaly views flag activity for a person to review. They do not determine who is flying, what the flight is for, or whether it is a threat. Those calls stay with your operators.
Pulling patterns into another system
The same pattern views are available from the Analytics API, each with a look-back window in hours:
curl http://<analytics-server>:8090/api/patterns/repeated-drones?hours=24
curl http://<analytics-server>:8090/api/patterns/coordinated?hours=6
curl http://<analytics-server>:8090/api/patterns/pilot-reuse?hours=12
curl http://<analytics-server>:8090/api/patterns/anomalies?hours=6
curl http://<analytics-server>:8090/api/patterns/multi-kit?hours=6Critical Do not expose the Analytics web interface, dashboards, or API to the public internet without a VPN.
If a view is empty
Confirm the kit appears in the Kit Manager and is reporting, then confirm the kit itself has detections by checking /drones on its API. See Adding a kit to WarDragon Analytics for what to check when a kit does not appear. Pattern and correlation views need history to work from, so a new installation shows little until detections build up.
Related
WarDragon is manufactured by Millenium Products Inc. Technical support for purchased kits is requested through the support page. Purchasing and quote requests go through the contact form.