A kit can be added to WarDragon Analytics from the web interface, from a configuration file, or by pushing over MQTT. This article covers each, and how to check that the Analytics server can actually reach the kit.
Before you add a kit
For polling, the Analytics server must be able to reach the kit’s API. From the Analytics server, confirm it responds:
curl http://<kit-ip>:8088/status
If that fails, fix the network path first. See Reading a detection: tracks, signal alerts, and the API.
From the web interface
- Open the Analytics web interface on port 8090.
- Choose Kit Manager in the sidebar.
- Enter the kit’s API address, for example
http://<kit-ip>:8088. - Choose Add Kit. The collector starts polling immediately.
Kits added this way are stored in the database and are still there after a restart.
From the configuration file
Edit config/kits.yaml on the Analytics server:
kits:
- api_url: "http://<kit-ip>:8088"
name: "Field Kit Alpha"
enabled: true
Then restart the collector so it loads the file:
docker compose restart collector
The web interface and the file can be used together. Kits in the file are loaded each time the collector starts.
By MQTT push
For kits that can only make outbound connections, use MQTT ingest instead of polling. Kits publish to the Analytics server and appear automatically the first time they do. On the Analytics server, enable it in .env and start the MQTT profile:
MQTT_INGEST_ENABLED=true
docker compose --profile mqtt up -d
Then point each kit’s MQTT output at the Analytics server on port 1883, using the settings in Checking that detections are reaching your MQTT broker.
If a kit does not appear
- Confirm the API address and port are correct and reachable from the Analytics server.
- Check the collector’s log:
docker compose logs -f collector - For a file entry, confirm
enabled: trueand that the collector was restarted.
Related
- WarDragon User Guide, Appendix A.3 — API endpoints
- WarDragon Analytics: what it is and where it runs
