The WSO2 EMM dashboard provides an overview of the devices, so that the administrators are able to manage registered devices efficiently and effectively. This section provides the details of the REST APIs used to get the summarized details.
Getting device connectivity status overview
Description | Get the details of active, inactive, removed and total number of registered devices in WSO2 EMM. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Resource Path | /device-count-overview | ||||||||||||
URL |
| ||||||||||||
HTTP Method | GET | ||||||||||||
Request/Response Format | application/json | ||||||||||||
cURL command | curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-admin/dashboard/device-count-overview
Example: curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c" -k -v https://localhost:9443/mdm-admin/dashboard/device-count-overview | ||||||||||||
Sample output | > GET /mdm-admin/dashboard/devices-count-overview HTTP/1.1 > User-Agent: curl/7.38.0 > Host: localhost:9443 > Accept: */* > Content-Type: application/json > Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c > < HTTP/1.1 200 OK < Cache-Control: private < Expires: Thu, 01 Jan 1970 05:30:00 IST < Date: Fri, 29 Apr 2016 11:32:49 GMT < Content-Type: application/json < Content-Length: 232 < Server: WSO2 Carbon Server [{"context":"connectivity-status","data":[{"group":"total","label":"Total","count":5},{"group":"active","label":"Active","count":4},{"group":"inactive","label":"Inactive","count":0},{"group":"removed","label":"Removed","count":1}]}] | ||||||||||||
Sample JSON Definition | [ { "context":"connectivity-status", "data":[ { "group":"total", "label":"Total", "count":5 }, { "group":"active", "label":"Active", "count":4 }, { "group":"inactive", "label":"Inactive", "count":0 }, { "group":"removed", "label":"Removed", "count":1 } ] } ]
|
Getting policy non-compliant overview
Description | Get the number of devices that have not complied to a policy that was enforced on a device. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Resource Path | non-compliant-device-counts-by-features | ||||||||||||
URL |
| ||||||||||||
HTTP Method | GET | ||||||||||||
Request/Response Format | application/json | ||||||||||||
cURL command | curl -v -L -G -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-admin/dashboard/non-compliant-device-counts-by-features -d "start=<START>&length=<LENGTH>"
If you wish to get the device details within a predefined index range, you need to define both the There will be situations were you will not have any details in the specified index range. In such situation all the details of the devices that have not complied to a given policy is given. Example: curl -v -L -G -H "Content-Type: application/json" -H "Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c" -k -v https://localhost:9443/mdm-admin/dashboard/non-compliant-device-counts-by-features -d "start=10&length=5" | ||||||||||||
Sample output | > GET /mdm-admin/dashboard/non-compliant-device-counts-by-features?start=0&length=5 HTTP/1.1 > User-Agent: curl/7.38.0 > Host: localhost:9443 > Accept: */* > Content-Type: application/json > Authorization: Bearer c148a833a9c3d30bb5197788eaad5541 > < HTTP/1.1 200 OK < Cache-Control: private < Expires: Thu, 01 Jan 1970 05:30:00 IST < Date: Sat, 30 Apr 2016 06:55:54 GMT < Content-Type: application/json < Content-Length: 184 * Server WSO2 Carbon Server is not blacklisted < Server: WSO2 Carbon Server < [{"context":"non-compliant-feature","data":[{"group":"PASSCODE_POLICY","label":"PASSCODE_POLICY","count":4},{"group":"WIFI","label":"WIFI","count":2}], "totalRecordCount":2}] | ||||||||||||
Sample JSON Output Definition | [ { "context":"non-compliant-feature", "data":[ { "group":"PASSCODE_POLICY", "label":"PASSCODE_POLICY", "count":4 }, { "group":"WIFI", "label":"WIFI", "count":2 } ], "totalRecordCount":2 } ]
|
Getting potential device vulnerability overview
Description | Get the number of unmonitored and non-compliant devices in WSO2 EMM. | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Resource Path | /device-counts-by-potential-vulnerabilities | ||||||||||||
URL |
| ||||||||||||
HTTP Method | GET | ||||||||||||
Request/Response Format | application/json | ||||||||||||
cURL command | curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-admin/dashboard/device-counts-by-potential-vulnerabilities
Example: curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c" -k -v https://localhost:9443/mdm-admin/dashboard/device-counts-by-potential-vulnerabilities | ||||||||||||
Sample output | > GET /mdm-admin/dashboard/device-counts-by-potential-vulnerabilities HTTP/1.1 > User-Agent: curl/7.38.0 > Host: localhost:9443 > Accept: */* > Content-Type: application/json > Authorization: Bearer 0ff0f5c5ef202f5abd933efef370a28c < HTTP/1.1 200 OK < Cache-Control: private < Expires: Thu, 01 Jan 1970 05:30:00 IST < Date: Sat, 30 Apr 2016 01:55:36 GMT < Content-Type: application/json < Content-Length: 164 < Server: WSO2 Carbon Server [{"context":"potential-vulnerability","data":[{"group":"non-compliant","label":"Non-Compliant","count":5},{"group":"unmonitored","label":"Unmonitored","count":0}]}] | ||||||||||||
Sample JSON Output Definition | [ { "context":"potential-vulnerability", "data":[ { "group":"non-compliant", "label":"Non-Compliant", "count":5 }, { "group":"unmonitored", "label":"Unmonitored", "count":0 } ] } ]
|