cisco.dnac.dhcp_services_id_trend_analytics_v1 module -- Resource module for Dhcp Services Id Trend Analytics V1
Note
This module is part of the cisco.dnac collection (version 6.30.2).
To install it, use: ansible-galaxy collection install cisco.dnac.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: cisco.dnac.dhcp_services_id_trend_analytics_v1.
New in cisco.dnac 6.17.0
Synopsis
Manage operation create of the resource Dhcp Services Id Trend Analytics V1.
Gets the trend analytics data related to a particular DHCP Service matching the id. For detailed information about the usage of the API, please refer to the Open API specification document - https //github.com/cisco-en- programmability/catalyst-center-api-specs/blob/main/Assurance/CE_Cat_Center_Org-DHCPServices-1.0.0-resolved.yaml.
Note
This module has a corresponding action plugin.
Requirements
The below requirements are needed on the host that executes this module.
dnacentersdk >= 2.4.9
python >= 3.5
Parameters
Parameter |
Comments |
|---|---|
Dhcp Services Id Trend Analytics's aggregateAttributes. |
|
Function. |
|
Name. |
|
Attributes. |
|
Flag for Cisco DNA Center SDK to enable debugging. Choices: |
|
The Cisco DNA Center hostname. |
|
The Cisco DNA Center password to authenticate. |
|
The Cisco DNA Center port. Default: :ansible-option-default:`443` |
|
The Cisco DNA 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 DNA Center to use. Default: :ansible-option-default:`"2.3.7.6"` |
|
End Time. |
|
Dhcp Services Id Trend Analytics's filters. |
|
Filters. |
|
Key. |
|
Logical Operator. |
|
Operator. |
|
Value. |
|
Group By. |
|
Additional headers. |
|
Id path parameter. Unique id of the DHCP Service. It is the combination of DHCP Server IP (`serverIp`) and Device UUID (`deviceId`) separated by underscore (`_`). Example If `serverIp` is `10.76.81.33` and `deviceId` is `6bef213c-19ca-4170-8375-b694e251101c`, then the `id` would be `10.76.81.33_6bef213c-19ca-4170-8375-b694e251101c`. |
|
Dhcp Services Id Trend Analytics's page. |
|
Limit. |
|
Offset. |
|
Timestamp Order. |
|
Start Time. |
|
Trend Interval. |
|
Flag for Cisco DNA Center SDK to enable the validation of request bodies against a JSON schema. Choices: |
Notes
Note
SDK Method used are devices.Devices.get_trend_analytics_data_for_a_given_d_h_c_p_service_matching_the_id_of_the_service_v1,
Paths used are post /dna/data/api/v1/dhcpServices/{id}/trendAnalytics,
Does not support
check_modeThe plugin runs on the control node and does not use any ansible connection plugins, but instead the embedded connection manager from Cisco DNAC SDK
The parameters starting with dnac_ are used by the Cisco DNAC Python SDK to establish the connection
See Also
See also
- Cisco DNA Center documentation for Devices GetTrendAnalyticsDataForAGivenDHCPServiceMatchingTheIdOfTheServiceV1
Complete reference of the GetTrendAnalyticsDataForAGivenDHCPServiceMatchingTheIdOfTheServiceV1 API.
Examples
- name: Create
cisco.dnac.dhcp_services_id_trend_analytics_v1:
dnac_host: "{{dnac_host}}"
dnac_username: "{{dnac_username}}"
dnac_password: "{{dnac_password}}"
dnac_verify: "{{dnac_verify}}"
dnac_port: "{{dnac_port}}"
dnac_version: "{{dnac_version}}"
dnac_debug: "{{dnac_debug}}"
aggregateAttributes:
- function: string
name: string
attributes:
- string
endTime: 0
filters:
- filters:
- string
key: string
logicalOperator: string
operator: string
value: {}
groupBy:
- string
headers: '{{my_headers | from_json}}'
id: string
page:
limit: 0
offset: 0
timestampOrder: string
startTime: 0
trendInterval: string
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 DNAC Python SDK Returned: always |