Skip to content

server_info

Configuration for server_info Resource resource.

(click to see Operations)

Properties

(click to see Operations)

NameData TypePermissionsDescription
report_end_time<Double>Read-writereport_end_time for getting the logs in milliseconds.
anomaly_data<anomaly_item[]>Read-writeList of anomalous values and their timestamp.
rpt_sample_time<Double>Read-write.
duration<String>Read-writeCalculation frequency period daily,weekly etc.
anomaly_count<Integer>Read-writeNumber of anomalies.
report_start_time<Double>Read-writereport_start_time for getting the logs in milliseconds.
id<String>Read-write.
server_name<String>Read-writeName of the Device.
server_ip<String>Read-writeDevice 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>.

get (all)

URL: https://<MGMT-IP>/nitro/v1/config/server_info

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "server_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>,
"report_start_time":<Double_value>,
"id":<String_value>,
"server_name":<String_value>,
"server_ip":<String_value>}]}

get

URL: https://<MGMT-IP>/nitro/v1/config/server_info/server_ip_value<String>

HTTP Method: null

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value>, "server_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>,
"report_start_time":<Double_value>,
"id":<String_value>,
"server_name":<String_value>,
"server_ip":<String_value>}]}