cisco.catalystcenter.wireless_controllers_stats_query_count_create module -- Resource module for Wireless Controllers Stats Query Count Create
Note
This module is part of the cisco.catalystcenter collection (version 2.12.0).
To install it, use: ansible-galaxy collection install cisco.catalystcenter.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.catalystcenter.wireless_controllers_stats_query_count_create.
New in cisco.catalystcenter 2.11.0
Synopsis
Manage operation create of the resource Wireless Controllers Stats Query Count Create. - > Retrieves the number of WLCs by applying complex filters. If startTime and endTime are not provided, the API defaults to the last 24 hours.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
catalystcentersdk >= 3.2.3.0.0
python >= 3.12
Parameters
Parameter |
Comments |
|---|---|
Flag for Cisco Catalyst Center SDK to enable debugging. Choices: |
|
The Cisco Catalyst Center hostname. |
|
The Cisco Catalyst Center password to authenticate. |
|
The Cisco Catalyst Center port. Default: :ansible-option-default:`443` |
|
The Cisco Catalyst Center username to authenticate. Default: :ansible-option-default:`"admin"` |
|
Flag to enable or disable SSL certificate verification. Choices: |
|
Informs the SDK which version of Cisco Catalyst Center to use. Default: :ansible-option-default:`"3.1.6.0"` |
|
End time to which the API queries the dataset related to the resource. It must be specified in terms of milliseconds since UNIX epoch. Value is inclusive. |
|
Wireless Controllers Stats Query Count Create's filters. |
|
Nested array of filters in case of AND/OR based filters. Only one level of nesting will be supported. Structure of nested filter is the same as parent with all operators supported except AND or OR. |
|
Nested array of filters in case of AND/OR based filters. Only one level of nesting will be supported. Structure of nested filter is the same as parent with all operators supported except AND or OR. |
|
Nested array of filters in case of AND/OR based filters. Only one level of nesting will be supported. Structure of nested filter is the same as parent with all operators supported except AND or OR. |
|
Nested array of filters in case of AND/OR based filters. Only one level of nesting will be supported. Structure of nested filter is the same as parent with all operators supported except AND or OR. |
|
Nested array of filters in case of AND/OR based filters. Only one level of nesting will be supported. Structure of nested filter is the same as parent with all operators supported except AND or OR. |
|
Supported filter attributes related to WlcStats. |
|
Operator to use when attempting to apply a logical conjunction of more than 1 filter Logical operations include 'and', 'or'. |
|
Type of filter operator to use for querying data | in and out operator takes multiple values and applies the filters. |
|
Field value(s) to filter the data set. Array of values is used for "in" or "out" operator. Values will be of whatever type the specific field being filtered is defined with. For other operators, filter value is of whatever type the specific field being filtered is defined with. In the case of an "and" or "or" operator, this values array will be ignored, and the values arrays in each of the *nested filters* will be used. The data type of a value, or each item inside the value in case it is a list, must match the type defined in the WlcStats response model. |
|
Supported filter attributes related to WlcStats. |
|
Operator to use when attempting to apply a logical conjunction of more than 1 filter Logical operations include 'and', 'or'. |
|
Type of filter operator to use for querying data | in and out operator takes multiple values and applies the filters. |
|
Field value(s) to filter the data set. Array of values is used for "in" or "out" operator. Values will be of whatever type the specific field being filtered is defined with. For other operators, filter value is of whatever type the specific field being filtered is defined with. In the case of an "and" or "or" operator, this values array will be ignored, and the values arrays in each of the *nested filters* will be used. The data type of a value, or each item inside the value in case it is a list, must match the type defined in the WlcStats response model. |
|
Supported filter attributes related to WlcStats. |
|
Operator to use when attempting to apply a logical conjunction of more than 1 filter Logical operations include 'and', 'or'. |
|
Type of filter operator to use for querying data | in and out operator takes multiple values and applies the filters. |
|
Field value(s) to filter the data set. Array of values is used for "in" or "out" operator. Values will be of whatever type the specific field being filtered is defined with. For other operators, filter value is of whatever type the specific field being filtered is defined with. In the case of an "and" or "or" operator, this values array will be ignored, and the values arrays in each of the *nested filters* will be used. The data type of a value, or each item inside the value in case it is a list, must match the type defined in the WlcStats response model. |
|
Supported filter attributes related to WlcStats. |
|
Operator to use when attempting to apply a logical conjunction of more than 1 filter Logical operations include 'and', 'or'. |
|
Type of filter operator to use for querying data | in and out operator takes multiple values and applies the filters. |
|
Field value(s) to filter the data set. Array of values is used for "in" or "out" operator. Values will be of whatever type the specific field being filtered is defined with. For other operators, filter value is of whatever type the specific field being filtered is defined with. In the case of an "and" or "or" operator, this values array will be ignored, and the values arrays in each of the *nested filters* will be used. The data type of a value, or each item inside the value in case it is a list, must match the type defined in the WlcStats response model. |
|
Supported filter attributes related to WlcStats. |
|
Operator to use when attempting to apply a logical conjunction of more than 1 filter Logical operations include 'and', 'or'. |
|
Type of filter operator to use for querying data | in and out operator takes multiple values and applies the filters. |
|
Field value(s) to filter the data set. Array of values is used for "in" or "out" operator. Values will be of whatever type the specific field being filtered is defined with. For other operators, filter value is of whatever type the specific field being filtered is defined with. In the case of an "and" or "or" operator, this values array will be ignored, and the values arrays in each of the *nested filters* will be used. The data type of a value, or each item inside the value in case it is a list, must match the type defined in the WlcStats response model. |
|
Additional headers. |
|
Start time from which the API queries the dataset related to the resource. It must be specified in terms of milliseconds since UNIX epoch. Value is inclusive. |
|
Flag for Cisco Catalyst Center SDK to enable the validation of request bodies against a JSON schema. Choices: |
Notes
Note
SDK Method used are devices.Devices.retrieves_the_number_of_wlcs_by_applying_complex_filters,
Paths used are post /dna/data/api/v1/wirelessControllersStats/query/count,
Does not support
check_modeThe plugin runs on the control node and does not use any ansible connection plugins,
but instead uses the embedded connection manager from Cisco CATALYST SDK
Requires Python >= 3.10, matching the controller Python versions supported by the collection's minimum ansible-core version (see the collection README for the current ansible-core / Python compatibility range)
See Also
See also
- Cisco Catalyst Center documentation for Devices RetrievesTheNumberOfWLCsByApplyingComplexFilters
Complete reference of the RetrievesTheNumberOfWLCsByApplyingComplexFilters API.
Examples
---
- name: Create
cisco.catalystcenter.wireless_controllers_stats_query_count_create:
catalystcenter_host: "{{catalystcenter_host}}"
catalystcenter_username: "{{catalystcenter_username}}"
catalystcenter_password: "{{catalystcenter_password}}"
catalystcenter_verify: "{{catalystcenter_verify}}"
catalystcenter_port: "{{catalystcenter_port}}"
catalystcenter_version: "{{catalystcenter_version}}"
catalystcenter_debug: "{{catalystcenter_debug}}"
endTime: 0
filters:
- filters:
- filters:
- filters:
- filters:
- filters:
- {}
key: string
logicalOperator: string
operator: string
value: {}
key: string
logicalOperator: string
operator: string
value: {}
key: string
logicalOperator: string
operator: string
value: {}
key: string
logicalOperator: string
operator: string
value: {}
key: string
logicalOperator: string
operator: string
value: {}
headers: '{{my_headers | from_json}}'
startTime: 0
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
A dictionary or list with the response returned by the Cisco Catalyst Center Python SDK Returned: always Sample: :ansible-rv-sample-value:`{"response": {"count": 0}, "version": "string"}` |