threshold_breach_timeline¶
Configuration for Af report for Threshold breach timeline resource.
Properties¶
(click to see Operations )
Name | Data Type | Permissions | Description |
---|---|---|---|
__count | <Double> | Read-write | Number of records. |
breach_metric | <String> | Read-write | all violated metric configured for entity. |
breach_entity_type | <String> | Read-write | threshold violated entity_type e.g App, Device. |
breach_value | <Double> | Read-write | threshold breached value. |
breach_count | <Double> | Read-write | breach_count.. |
rpt_sample_time | <Double> | Read-write | Timestamp of record. |
breach_entity | <String> | Read-write | threshold violated entity e.g outlook. |
Operations¶
(click to see Properties )
- GET (ALL)
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/threshold_breach_timeline
Query-parameters:
cr_enabled Use this query-parameter to indicate cr is enabled or not.
Possible Values: 0, 1
report_start_time Use this query-parameter to specify the start time from which the summary for report is considered.
Possible Values: time in milli seconds
report_end_time Use this query-parameter to specify the end time until where summary for report is considered.
Possible Values: time in milli seconds
sla_enabled Use this query-parameter to indicate sla is enabled or not.
Possible Values: 0, 1
type Use this query-parameter to specify the type.
Possible Values: ica_rtt, timeline_user_count, license_in_use
HTTPS Method: GET
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, "threshold_breach_timeline":[{
"__count":<Double_value>,
"breach_metric":<String_value>,
"breach_entity_type":<String_value>,
"breach_value":<Double_value>,
"breach_count":<Double_value>,
"rpt_sample_time":<Double_value>,
"breach_entity":<String_value>}]}