Data Usage Available Methods
Written by Mitchell Ivany
Updated at March 15th, 2025
- Our Products & Services
- Getting Started
- Accounts
- Communication
- Billing
- Companies
- Financial
- Integrations
- Inventory
- Jobs
- Mapping
- Misc.
- Monitoring
- Purchase Orders
- Release Notes
- Sonar Billing
- Voice
- Reporting
- Security
- sonarPay
- Ticketing
- Working With the Sonar Team & Additional Resources
- System
- Networking
Table of Contents
Data Usage Available Methods
When it comes to bringing Usage Data into Sonar there are a variety of methods that may be applied. More than one method may be applied at the same time to aggregate all data. A brief summary of each method, as well as links to that methods setup, are available below:
RADIUS Accounting
When a RADIUS session is terminated, usage data from the radacct tables in your RADIUS server is transferred to any accounts where that RADIUS username is stored.
Netflow Endpoints
Netflow data from any inline device capable of producing this data is added into Sonar accounts based on the Src. IPs and Dst. IPs being assigned to a device on an account or to the account itself.
Currently only available in V1 but will be coming to V2 soon.
Preseem
Usage data is collected by the Preseem appliance and gets associated to accounts in Sonar based on IPs being assigned to a device on an account or to the account itself.
PacketLogic
Usage data is collected by the PacketLogic appliance and gets associated to accounts in Sonar based on IPs being assigned to a device on an account or to the account itself.
SaiSei
Usage data is collected by the SaiSei appliance and gets associated to accounts in Sonar based on IPs being assigned to a device on an account or to the account itself.
API
Data gets driven back to an account based on API endpoints that reference the account ID. Typically a middleware server aggregates this usage from one or more sources, then writes it into Sonar periodically.