sensu.sensu_go.filter – Manage Sensu filters
Note
This plugin is part of the sensu.sensu_go collection (version 1.12.0).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install sensu.sensu_go
.
To use it in a playbook, specify: sensu.sensu_go.filter
.
New in version 1.0.0: of sensu.sensu_go
Synopsis
Create, update or delete Sensu filter.
For more information, refer to the Sensu documentation at https://docs.sensu.io/sensu-go/latest/reference/filters/.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.7
Parameters
Parameter |
Comments |
---|---|
Action to take with the event if the filter expressions match. Required if state is Choices:
|
|
Custom metadata fields with fewer restrictions, as key/value pairs. These are preserved by Sensu but not accessible as tokens or identifiers, and are mainly intended for use with external tools. |
|
Authentication parameters. Can define each of them with ENV as well. |
|
The API key that should be used when authenticating. If this is not set, the value of the SENSU_API_KEY environment variable will be checked. This replaces auth.user and auth.password parameters. For more information about the API key, refer to the official Sensu documentation at https://docs.sensu.io/sensu-go/latest/guides/use-apikey-feature/. |
|
Path to the CA bundle that should be used to validate the backend certificate. If this parameter is not set, module will use the CA bundle that python is using. It is also possible to set this parameter via the SENSU_CA_PATH environment variable. |
|
The Sensu user’s password. If this is not set the value of the SENSU_PASSWORD environment variable will be checked. This parameter is ignored if the auth.api_key parameter is set. Default: “P@ssw0rd!” |
|
Location of the Sensu backend API. If this is not set the value of the SENSU_URL environment variable will be checked. Default: “http://localhost:8080” |
|
The username to use for connecting to the Sensu API. If this is not set the value of the SENSU_USER environment variable will be checked. This parameter is ignored if the auth.api_key parameter is set. Default: “admin” |
|
Flag that controls the certificate validation. If you are using self-signed certificates, you can set this parameter to ONLY USE THIS PARAMETER IN DEVELOPMENT SCENARIOS! In you use self-signed certificates in production, see the auth.ca_path parameter. It is also possible to set this parameter via the SENSU_VERIFY environment variable. Choices:
|
|
Filter expressions to be compared with event data. Required if state is |
|
Custom metadata fields that can be accessed within Sensu, as key/value pairs. |
|
The Sensu resource’s name. This name (in combination with the namespace where applicable) uniquely identifies the resource that Ansible operates on. If the resource with selected name already exists, Ansible module will update it to match the specification in the task. Consult the name metadata attribute specification in the upstream docs on https://docs.sensu.io/sensu-go/latest/reference/ for more details about valid names and other restrictions. |
|
RBAC namespace to operate in. If this is not set the value of the SENSU_NAMESPACE environment variable will be used. Default: “default” |
|
Assets to be applied to the filter’s execution context. JavaScript files in the lib directory of the asset will be evaluated. |
|
Target state of the Sensu object. Choices:
|
See Also
See also
- sensu.sensu_go.filter_info
The official documentation on the sensu.sensu_go.filter_info module.
Examples
- name: Create a filter
sensu.sensu_go.filter:
name: filter
action: deny
expressions:
- event.check.interval == 10
- event.check.occurrences == 1
runtime_assets: awesomeness
- name: Create a production filter
sensu.sensu_go.filter:
name: filter
action: allow
expressions:
- event.entity.labels['environment'] == 'production'
- name: Create a filter with JS expression
sensu.sensu_go.filter:
name: filter
action: deny
expressions:
- "_.reduce(event.check.history, function(memo, h) { return (memo || h.status != 0); })"
runtime_assets:
- underscore
- name: Handling repeated events
sensu.sensu_go.filter:
name: filter_interval_60_hourly
action: allow
expressions:
- event.check.interval == 60
- event.check.occurrences == 1 || event.check.occurrences % 60 == 0
- name: Delete a filter
sensu.sensu_go.filter:
name: filter_interval_60_hourly
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Object representing Sensu filter. Returned: success Sample: {“action”: “allow”, “expressions”: [“event.check.occurrences == 1”], “metadata”: {“name”: “filter_minimum”, “namespace”: “default”}} |
Authors
Paul Arthur (@flowerysong)
Aljaz Kosir (@aljazkosir)
Miha Plesko (@miha-plesko)
Tadej Borovsak (@tadeboro)