The OpenWiFi Analytics Service (OWANALYTICS) is a core microservice within the Telecom Infra Project (TIP) OpenWiFi CloudSDK (OWSDK) ecosystem.
OWANALYTICS gathers real-time statistics and telemetry reports from connected devices, aggregating metrics (like CPU load, memory usage, radio noise, and client associations) and grouping them logically according to their provisioning entities or venues.
This service is part of Mango Cloud, Router Architects’ open-source platform for managed Wi-Fi and connectivity operations.
Within Mango Cloud, OWANALYTICS serves as the central Device Analytics & Telemetry Aggregator.
Key integrations include:
- AP Status Tracker: Listens to periodic status/telemetry payloads sent by Access Points via the Controller Service (
owgw). - KPI Metrics Calculator: Aggregates CPU load, memory, temperature, and channel noise profiles, grouping them by MDU property or venue to generate historical graphs.
- Client Association Logger: Records client connection history, data bandwidth (Rx/Tx bytes), signal strengths (RSSI), and MCS rates across 2G/5G/6G radio bands.
- Intra-Microservice Auth: Uses access tokens issued by the Security Service (
owsec) to secure telemetry validation APIs.
The OpenAPI definition is available directly in the GitHub repository. You can load the raw OpenAPI definition file into Swagger UI to view interactive API docs.
To build the microservice from source, please follow the instructions in BUILDING.md.
To run this service as part of the CloudSDK containerized deployment, refer to the mango-cloud-deployment repository instructions.
The microservice exposes three main network interfaces. Ensure your firewall or container ingress rules are configured accordingly:
| Port | Description | Configurable |
|---|---|---|
16009 |
Default port for public REST API Access to the OWANALYTICS | yes |
17009 |
Default port for internal REST API Access (intra-service communications) | yes |
16109 |
Default port for Application Load Balancer (ALB) Health Checks | yes |
All configuration parameters are stored in the owanalytics.properties file. For a complete guide to all available properties, check CONFIGURATION.md.
The service uses Kafka to ingest device telemetry payloads and coordinate with other microservices. To read more about the Kafka integration, review KAFKA.md.
We welcome and appreciate community contributions. Please review CONTRIBUTING.md to get started.
When submitting pull requests:
- Create a branch named after the JIRA issue you are resolving or the feature you are implementing.
- Submit your pull request targeting the
mainbranch.
Here is the index of additional OpenWiFi microservices:
| Name | Description | Link | OpenAPI |
|---|---|---|---|
| OWSEC | Security Service | here | here |
| OWGW | Controller Service | here | here |
| OWFMS | Firmware Management Service | here | here |
| OWPROV | Provisioning Service | here | here |
| OWANALYTICS | Analytics Service | here | here |
| OWSUB | Subscriber Portal Service | here | here |
| NW-Topology | Network Topology Service | here | here |
