cisco.meraki.meraki_alert module -- Manage alerts in the Meraki cloud
Note
This module is part of the cisco.meraki collection (version 2.18.2).
To install it, use: ansible-galaxy collection install cisco.meraki
.
To use it in a playbook, specify: cisco.meraki.meraki_alert
.
New in cisco.meraki 2.1.0
DEPRECATED
- Removed in:
version 3.0.0
- Why:
Updated modules released with increased functionality
- Alternative:
cisco.meraki.networks_alerts_settings
Synopsis
Allows for creation, management, and visibility into alert settings within Meraki.
Parameters
Parameter |
Comments |
---|---|
Alert-specific configuration for each type. |
|
A hash of destinations for this specific alert. |
|
If true, all network admins will receive emails. Choices: |
|
A list of emails that will recieve the alert(s). |
|
A list of HTTP server IDs to send a Webhook to. |
|
If true, then an SNMP trap will be sent if there is an SNMP trap server configured for this network. Choices: |
|
The type of alert. |
|
A boolean depicting if the alert is turned on or off. Choices: |
|
A hash of specific configuration data for the alert. Only filters specific to the alert will be updated. No validation checks occur against Default: :ansible-option-default:`{}` |
|
Authentication key provided by the dashboard. Required if environmental variable |
|
Properties for destinations when alert specific destinations aren't specified. |
|
If true, all network admins will receive emails. Choices: |
|
A list of emails that will recieve the alert(s). |
|
A list of HTTP server IDs to send a Webhook to. |
|
If true, then an SNMP trap will be sent if there is an SNMP trap server configured for this network. Choices: |
|
Hostname for Meraki dashboard. Can be used to access regional Meraki environments, such as China. |
|
Number of seconds to retry if server returns an internal server error. Default: :ansible-option-default:`60` |
|
ID number of a network. |
|
Name of a network. |
|
ID of organization. |
|
Name of organization. |
|
Instructs module whether response keys should be snake case (ex. Choices: |
|
Set amount of debug output during module execution. Choices: |
|
Number of seconds to retry if rate limiter is triggered. Default: :ansible-option-default:`165` |
|
Create or modify an alert. Choices: |
|
Time to timeout for HTTP requests. Default: :ansible-option-default:`30` |
|
If Only useful for internal Meraki developers. Choices: |
|
If Choices: |
|
Whether to validate HTTP certificates. Choices: |
Notes
Note
More information about the Meraki API can be found at https://dashboard.meraki.com/api_docs.
Some of the options are likely only used for developers within Meraki.
As of Ansible 2.9, Meraki modules output keys as snake case. To use camel case, set the
ANSIBLE_MERAKI_FORMAT
environment variable tocamelcase
.Ansible's Meraki modules will stop supporting camel case output in Ansible 2.13. Please update your playbooks.
Check Mode downloads the current configuration from the dashboard, then compares changes against this download. Check Mode will report changed if there are differences in the configurations, but does not submit changes to the API for validation of change.
Examples
- name: Update settings
meraki_alert:
auth_key: abc123
org_name: YourOrg
net_name: YourNet
state: present
default_destinations:
emails:
- 'youremail@yourcorp'
- 'youremail2@yourcorp'
all_admins: yes
snmp: no
alerts:
- alert_type: "gatewayDown"
enabled: yes
filters:
timeout: 60
alert_destinations:
emails:
- 'youremail@yourcorp'
- 'youremail2@yourcorp'
all_admins: yes
snmp: no
- alert_type: "usageAlert"
enabled: yes
filters:
period: 1200
threshold: 104857600
alert_destinations:
emails:
- 'youremail@yourcorp'
- 'youremail2@yourcorp'
all_admins: yes
snmp: no
- name: Query all settings
meraki_alert:
auth_key: abc123
org_name: YourOrg
net_name: YourNet
state: query
delegate_to: localhost
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Information about the created or manipulated object. Returned: info |
|
Alert-specific configuration for each type. Returned: success |
|
A hash of destinations for this specific alert. Returned: success |
|
If true, all network admins will receive emails. Returned: success |
|
A list of emails that will recieve the alert(s). Returned: success |
|
A list of HTTP server IDs to send a Webhook to. Returned: success |
|
If true, then an SNMP trap will be sent if there is an SNMP trap server configured for this network. Returned: success |
|
The type of alert. Returned: success |
|
A boolean depicting if the alert is turned on or off. Returned: success |
|
A hash of specific configuration data for the alert. Only filters specific to the alert will be updated. No validation checks occur against Returned: success |
|
Properties for destinations when alert specific destinations aren't specified. Returned: success |
|
If true, all network admins will receive emails. Returned: success Sample: :ansible-rv-sample-value:`true` |
|
A list of emails that will recieve the alert(s). Returned: success |
|
A list of HTTP server IDs to send a Webhook to. Returned: success |
|
If true, then an SNMP trap will be sent if there is an SNMP trap server configured for this network. Returned: success Sample: :ansible-rv-sample-value:`true` |
Status
This module will be removed in version 3.0.0. [deprecated]
For more information see DEPRECATED.