Skip to content
Was this article helpful?


Configuration for event history resource.


(click to see Operations)

Name Data Type PermissionsDescription
starttime<String>Read-writeSpecify start time in mmddyyyyhhmm to start collecting values from that timestamp.
endtime<String>Read-writeSpecify end time in mmddyyyyhhmm upto which values have to be collected.
last<Integer>Read-writeLast is literal way of saying a certain time period from the current moment. Example: -last 1 hour, -last 1 day, et cetera.<br>Default value: 1
unit<String>Read-writeSpecify the time period from current moment. Example 1 x where x = hours/ days/ years.<br>Possible values = HOURS, DAYS, MONTHS
datasource<String>Read-writeSpecifies the source which contains all the stored counter values.


(click to see Properties)


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:


    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:



    Note: In such cases, make sure that the request header DOES not include the following:



Mandatory parameters are marked in red and placeholder content is marked in <green>.

get (all)

URL: http://<netscaler-ip-address>/nitro/v1/config/systemeventhistory




Use this query-parameter to get systemeventhistory resources based on additional properties.

HTTP Method: GET

Request Headers:

Cookie:NITRO_AUTH_TOKEN=<tokenvalue> Accept:application/json


HTTP Status Code on Success: 200 OK HTTP Status Code on Failure: 4xx <string> (for general HTTP errors) or 5xx <string> (for NetScaler-specific errors). The response payload provides details of the errorResponse Headers:


Response Payload:

{ "systemeventhistory": [ {
starttime:<String_value>,endtime:<String_value>,last:<Integer_value>,unit:<String_value>,datasource:<String_value>,      "response":<String_value>
Was this article helpful?