Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
You also can query other control metrics by specifying the control metric type such as cpu, memory, disk, network, etc.
REST API
We also provide a way to query and collect control metrics through REST API.
Followings are the REST API for collecting and querying control metrics.
Collector
| POST /collector/cpu_metrics | Collects CPU metrics. |
| POST /collector/network_metrics | Collects network I/O metrics include in/out-bound packets/bytes statistics. |
| POST /collector/disk_metrics | Collects disk I/O metrics include read and write bytes. |
| POST /collector/system_info | Collects system information. |
| POST /collector/memory_metrics | Collects memory metrics. |
Control Metrics
| GET /controlmetrics/memory_metrics | List memory metrics of all network resources. |
| GET /controlmetrics/messages | List control message metrics of all devices. |
| GET /controlmetrics/messages/{deviceId} | List control message metrics of a given device. |
| GET /controlmetrics/cpu_metrics | List CPU metrics. |
| GET /controlmetrics/disk_metrics | List disk metrics of all disk resources. |
Web Graphic User Interface (GUI)
...
The second way is push based approach with which ONOS periodically report reports a set of control metrics to predefined third-party system.
By far, ONOS supports three systems and those are InfluxDB, ganglia and graphite monitoring system.
The detailed explanation on exporting the metrics to those system can be referred from following links.
Appendix