device_info
Configuration for device_info Resource resource.
Properties
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
report_end_time | <Double> | Read-write | report_end_time for getting the logs in milliseconds. |
anomaly_data | <anomaly_item[]> | Read-write | List of anomalous values and their timestamp. |
rpt_sample_time | <Double> | Read-write | . |
duration | <String> | Read-write | Calculation frequency period daily,weekly etc. |
anomaly_count | <Integer> | Read-write | Number of anomalies. |
device_name | <String> | Read-write | Name of the Device. |
report_start_time | <Double> | Read-write | report_start_time for getting the logs in milliseconds. |
id | <String> | Read-write | . |
server_ip | <String> | Read-write | Device IP Address.
Minimum length = 1 Maximum length = 64 |
Operations
(click to see Properties )
- GET (ALL)
- GET
Some options that you can use for each operations:
-
Getting warnings in response: NITRO allows you to get warnings in an operation by specifying the 'warning' query parameter as 'yes'. For example, to get warnings while connecting to the NetScaler appliance, the URL is as follows:
http:// <netscaler-ip-address> /nitro/v1/config/login?warning=yes
If any, the warnings are displayed in the response payload with the HTTP code '209 X-NITRO-WARNING'.
-
Authenticated access for individual NITRO operations: NITRO allows you to logon to the NetScaler appliance to perform individual operations. You can use this option instead of creating a NITRO session (using the login object) and then using that session to perform all operations,
To do this, you must specify the username and password in the request header of the NITRO request as follows:
X-NITRO-USER: <username>
X-NITRO-PASS: <password>
Note: In such cases, make sure that the request header DOES not include the following:
Cookie:NITRO_AUTH_TOKEN= <tokenvalue>
*Note:
*
Mandatory parameters are marked in
red
and placeholder content is marked in
green
The following parameters can be used in the nitro request : onerror <String_value>
Use this parameter to set the onerror status for nitro request. Applicable only for bulk requests.
Default value: EXIT
Possible values = EXIT, CONTINUE
get (all)
URL: https://<MGMT-IP>/nitro/v2/config/device_info Query-parameters:
filter https://<MGMT-IP>/nitro/v2/config/device_info ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of device_info resources configured on the system. You can set a filter on any property of the resource.
pagesize=#no;pageno=#no https://<MGMT-IP>/nitro/v2/config/device_info ?pagesize=#no;pageno=#no Use this query-parameter to get the device_info resources in chunks.
count https://<MGMT-IP>/nitro/v2/config/device_info ?count=yes Use this query-parameter to get the count of device_info resources.
HTTPS Method: GET
Request Headers: Accept: application/json
X-NITRO-USER:username_value<String>
X-NITRO-PASS:password_value<String>
or
Cookie:NITRO_AUTH_TOKEN=token_value<String>
Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error
Response Headers:
Content-Type:application/json
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "device_info":[{
"report_end_time":<Double_value>,
"anomaly_data":[{
"timestamp":<Double_value>,
"parent_name":<String_value>,
"value":<Double_value>,
"counter":<String_value>,
"id":<String_value>,
"parent_id":<String_value>}],
"rpt_sample_time":<Double_value>,
"duration":<String_value>,
"anomaly_count":<Integer_value>,
"device_name":<String_value>,
"report_start_time":<Double_value>,
"id":<String_value>,
"server_ip":<String_value>}]}
<!--NeedCopy-->
get
URL: https://<MGMT-IP>/nitro/v2/config/device_info/server_ip_value<String> HTTPS Method: GET
Request Headers: Accept: application/json
X-NITRO-USER:username_value<String>
X-NITRO-PASS:password_value<String>
or
Cookie:NITRO_AUTH_TOKEN=token_value<String>
Response: HTTPS Status Code on Success: 200 OK HTTPS Status Code on Failure: 4xx (for general HTTPS errors) or 5xx (for NetScaler-MAS-specific errors). The response payload provides details of the error
Response Headers:
Content-Type:application/json
Response Payload:
{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "device_info":[{
"report_end_time":<Double_value>,
"anomaly_data":[{
"timestamp":<Double_value>,
"parent_name":<String_value>,
"value":<Double_value>,
"counter":<String_value>,
"id":<String_value>,
"parent_id":<String_value>}],
"rpt_sample_time":<Double_value>,
"duration":<String_value>,
"anomaly_count":<Integer_value>,
"device_name":<String_value>,
"report_start_time":<Double_value>,
"id":<String_value>,
"server_ip":<String_value>}]}
<!--NeedCopy-->