-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature] RADIUS Timeseries Charts #532
Comments
The integration will write to the user signup metric in two conditions:
Now considering this scenario where a user is member of two organizations, two points will be written to the InfluxDB (one for each organization). When a superuser will look at the user registration chart on the dashboard, it will show twice the number of users: Is this side-effect correct? |
Good catch, when counting the amount of users for superusers, can we do a distinct on the field which identifies the user? So we discard the same user being subscribed to multiple organizations? |
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client Related to #532
- Added option to define "summary_query" for metrics - Added functionality to handle "GROUP by tags" clause to InfluxDB client - Added support to override metrics added with register_metric method - Added setting to set the DEFAULT_CHART_TIME - Added option to specify trace labels Related to #532
Implemented in openwisp/openwisp-radius#488. |
A number of changes will be made to the OpenWISP RADIUS and OpenWISP Monitoring modules which will make it possible to store RADIUS session data in anonymised form (i.e. personal user data contained in RADIUS session details will be obfuscated with hashing techniques such as "sha1") and user registrations, this will allow a retention of statistical data beyond 12/18 months for analysis purposes by the user without violating privacy and data retention laws.
The data will be stored in the timeseries database (InfluxDB) according to the already adopted retention policy which can be changed upon request.
This feature must be disabled by default and implemented in a separate optional sub module of openwisp-radius (in a similar way as we have created an integration modules in network-topology).
The snapshotting of the radius accounting sessions into influxdb could be done each time a radius session is flagged as closed.
The snapshotting of total sign ups could be done daily at the end of each day.
The daily sign ups timeseries data could be stored whenever a new user signs up and completes the verification process, or it could be taken at the end of each day too, as long as the solution meets the requirements and it's scalable we can be flexible with the implementation details.
Time Period
It will be possible to change the period of the timeseries data by going back in time, the minimum period that can be viewed will be one day, the maximum period that can be viewed will be a year, it will be possible to select the dates of interest and the grouping of statistical data over a long period will be one day, i.e. each point on the graph will represent a specific date.
CSV export
It will also be possible to export the data in CSV format, similar to how it already happens for the monitoring data of the devices.
The graphs that will be added are listed below and indicative graphical examples are provided.
Permission to view statistics (read only)
The system will allow the definition of user profiles who will have read-only access to the administration interface who will be able to view the statistical data without making any changes.
New daily sign up charts
It will allow to obtain the following information:
Cumulative sign ups charts
It will allow to obtain the following information:
RADIUS session traffic
It will allow to obtain the following information:
RADIUS sessions count
It will allow to obtain the following information:
Access and traffic statistics by device
The statistical data of the RADIUS sessions will also be shown on the WiFi devices page, it will therefore be possible to know, for each device:
Ability to filter general data by organization
On the main page of the system, users will be able to view and export the data of all organizations they have access to.
If the user has access to multiple organizations, the system will present the following possibilities:
The text was updated successfully, but these errors were encountered: