Aryaman
Aryaman
Closes #391 Checks: - [x] I have manually tested the proposed changes - [ ] I have written new test cases to avoid regressions (if necessary) - [ ] I...
   Closes #424 Closes #426 Checks: - [x] I have manually tested the proposed changes - [x] I have...
- This change will add possibility to check `alert threshold` on the specific metric field if provided in configuration otherwise, it uses `field_name`, which is current alert behaviour. - Removed...
Closes #416 Checks: - [x] I have manually tested the proposed changes - [x] I have written new test cases to avoid regressions (if necessary) - [x] I have updated...
- One server is not enough for larger systems, We must **specify multiple list** of Iperf servers. - User can configure multiple iperf servers corresponding to `organization` ```py # settings.py...
Reported by @pandafy in https://github.com/openwisp/openwisp-monitoring/pull/394#issuecomment-1202118479 - If we look below `stackedbar+lines` charts, time interval starts from **August 1 12:00 hrs with 12 hrs** time difference between each points on the...
- Currently, we support adaptive charts for `traffic charts`, We need to leverage that feature to support `iperf charts` as well. ### Possible Solution - If we look at the...
Acc to @nemesisdesign https://github.com/openwisp/openwisp-monitoring/pull/394#discussion_r927595377, We can compress all `iperf check` into a **single setting** (look below), so that it can be easily maintained. ### `Single Iperf check settings (example)`: ```py...
- With this enhancement, the user can use **RSA authentication** between the **client** and the **server** to restrict the connections to the server **only to legitimate clients.** - We can...
- If we look at current implementation of alerts, We see that alerts checks thresholds on only `value/field_name`, it would be nice if we can add alert functionality for `extra_values/related_fields`...