NetScaler SDX 13.1 NITRO API Reference

filter_scheduler

March 20, 2024

Contributed by:

Configuration for Filter Scheduler resource.

Properties

(click to see Operations )

Name	Data Type	Permissions	Description
details	<filter_schedule_details[]>	Read-write	Filter Schedule Details.
recurrence_type		Read-write	Type of recurrence of schedule for the filter : daily/weekly/specific day. Maximum length = 255
tz_offset		Read-write	Time zone offset..
filter_job_name		Read-write	Filter Job Name. Maximum length = 255
recurrenceOptions		Read-write	Comma separated recurrence options of job that is scheduled.
id		Read-write	Id is system generated key for all the events.
filter_status		Read-write	filter status - enabled, disabled, pause. Maximum length = 255
activity_log		Read-only	Activity description.
activity_status		Read-only	Activity Status.

Operations

(click to see Properties )

ADD
DELETE
GET (ALL)
GET
UPDATE

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

add

URL: https://<MGMT-IP>/nitro/v2/config/filter_scheduler?onerror=<String_value> HTTPS Method: POST

Request Headers: Content-Type: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Request Payload:

{"filter_scheduler": {
"filter_job_name":<String_value>,
"id":<String_value>,
"details":[{
"scheduleStartTimesEpoch":<String_value>,
"scheduleEndTimesEpoch":<String_value>,
"parent_id":<String_value>,
"id":<String_value>,
"endRecurrenceTimes":<String_value>,
"parent_name":<String_value>,
"startRecurrenceTimes":<String_value>}],
"tz_offset":<Integer_value>,
"recurrenceOptions":<String_value>,
"filter_status":<String_value>,
"recurrence_type":<String_value>}}

<!--NeedCopy-->

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 Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "filter_scheduler":[{
"details":[{
"scheduleEndTimesEpoch":<String_value>,
"scheduleStartTimesEpoch":<String_value>,
"parent_name":<String_value>,
"endRecurrenceTimes":<String_value>,
"id":<String_value>,
"startRecurrenceTimes":<String_value>,
"parent_id":<String_value>}],
"recurrence_type":<String_value>,
"tz_offset":<Integer_value>,
"activity_log":<String_value>,
"filter_job_name":<String_value>,
"recurrenceOptions":<String_value>,
"activity_status":<String_value>,
"id":<String_value>,
"filter_status":<String_value>}]}

<!--NeedCopy-->

delete

URL: https://<MGMT-IP>/nitro/v2/config/filter_scheduler/id_value<String> HTTPS Method: DELETE

Request Headers: X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt }

<!--NeedCopy-->

get (all)

URL: https://<MGMT-IP>/nitro/v2/config/filter_scheduler Query-parameters:

filter https://<MGMT-IP>/nitro/v2/config/filter_scheduler ?filter=property-name1:property-value1,property-name2:property-value2 Use this query-parameter to get the filtered set of filter_scheduler 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/filter_scheduler ?pagesize=#no;pageno=#no Use this query-parameter to get the filter_scheduler resources in chunks.

count https://<MGMT-IP>/nitro/v2/config/filter_scheduler ?count=yes Use this query-parameter to get the count of filter_scheduler resources.

HTTPS Method: GET

Request Headers: Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response Headers:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "filter_scheduler":[{
"details":[{
"scheduleEndTimesEpoch":<String_value>,
"scheduleStartTimesEpoch":<String_value>,
"parent_name":<String_value>,
"endRecurrenceTimes":<String_value>,
"id":<String_value>,
"startRecurrenceTimes":<String_value>,
"parent_id":<String_value>}],
"recurrence_type":<String_value>,
"tz_offset":<Integer_value>,
"activity_log":<String_value>,
"filter_job_name":<String_value>,
"recurrenceOptions":<String_value>,
"activity_status":<String_value>,
"id":<String_value>,
"filter_status":<String_value>}]}

<!--NeedCopy-->

get

URL: https://<MGMT-IP>/nitro/v2/config/filter_scheduler/id_value<String> HTTPS Method: GET

Request Headers: Accept: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Response Headers:

Content-Type:application/json

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "filter_scheduler":[{
"details":[{
"scheduleEndTimesEpoch":<String_value>,
"scheduleStartTimesEpoch":<String_value>,
"parent_name":<String_value>,
"endRecurrenceTimes":<String_value>,
"id":<String_value>,
"startRecurrenceTimes":<String_value>,
"parent_id":<String_value>}],
"recurrence_type":<String_value>,
"tz_offset":<Integer_value>,
"activity_log":<String_value>,
"filter_job_name":<String_value>,
"recurrenceOptions":<String_value>,
"activity_status":<String_value>,
"id":<String_value>,
"filter_status":<String_value>}]}

<!--NeedCopy-->

update

URL: https://<MGMT-IP>/nitro/v2/config/filter_scheduler/id_value<String> HTTPS Method: PUT

Request Headers: Content-Type: application/json

X-NITRO-USER:username_value<String>

X-NITRO-PASS:password_value<String>

Cookie:NITRO_AUTH_TOKEN=token_value<String>

Request Payload:

{"filter_scheduler":{
<b>"id":<String_value></b>,
"filter_job_name":<String_value>,
"details":[{
"scheduleStartTimesEpoch":<String_value>,
"scheduleEndTimesEpoch":<String_value>,
"parent_id":<String_value>,
"id":<String_value>,
"endRecurrenceTimes":<String_value>,
"parent_name":<String_value>,
"startRecurrenceTimes":<String_value>}],
"tz_offset":<Integer_value>,
"recurrenceOptions":<String_value>,
"filter_status":<String_value>,
"recurrence_type":<String_value>}}

<!--NeedCopy-->

Response Payload:

{ "errorcode": 0, "message": "Done", "severity": ;ltString_value;gt, "filter_scheduler":[{
"details":[{
"scheduleEndTimesEpoch":<String_value>,
"scheduleStartTimesEpoch":<String_value>,
"parent_name":<String_value>,
"endRecurrenceTimes":<String_value>,
"id":<String_value>,
"startRecurrenceTimes":<String_value>,
"parent_id":<String_value>}],
"recurrence_type":<String_value>,
"tz_offset":<Integer_value>,
"activity_log":<String_value>,
"filter_job_name":<String_value>,
"recurrenceOptions":<String_value>,
"activity_status":<String_value>,
"id":<String_value>,
"filter_status":<String_value>}]}

<!--NeedCopy-->

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

filter_scheduler

March 20, 2024

Contributed by:

March 20, 2024

Contributed by:

filter_scheduler

Properties

Operations

add

delete

get (all)

get

update

In this article