zlopez/ansible
1
0
Fork 0
forked from infra/ansible
Code Pull requests Activity

Fix yamllint trailing-spaces errors by removing trailing whitespace

Browse source 
Remove all trailing spaces from YAML files to comply with yamllint
formatting requirements.

Signed-off-by: Ryan Lerch <rlerch@redhat.com>
This commit is contained in:
Ryan Lerch 2026-02-24 10:45:08 +10:00 • committed by Kevin Fenzi
commit 4e70adc8d4
21 changed files with 127 additions and 127 deletions
Download patch file Download diff file Expand all files Collapse all files

4
playbooks/groups/ipatuura.yml
View file

@ -55,8 +55,8 @@
handlers:
- import_tasks: "{{ handlers_path }}/restart_services.yml"
# - name: Deploy
#  hosts: ipatuura_stg
# - name: Deploy
# hosts: ipatuura_stg
#  user: root
#  gather_facts: true
# 

8
playbooks/zabbix_maintenance.yml
View file

@ -1,6 +1,6 @@
---
# Zabbix Maintenance Window Playbook
# Usage:
# Usage:
# ansible-playbook zabbix_maintenance.yml -e "state=present"
# ansible-playbook zabbix_maintenance.yml -e "state=absent"
@ -12,7 +12,7 @@
- /srv/web/infra/ansible/vars/global.yml
- "/srv/private/ansible/vars.yml"
- /srv/web/infra/ansible/vars/{{ ansible_distribution }}.yml
vars:
ansible_zabbix_auth_key: "{{ zabbix_auth_key }}"
ansible_network_os: "{{ zabbix_network_os }}"
@ -25,12 +25,12 @@
state: "present" # present or absent
maintenance_name: Manual shush window
# Choose ONE of these target methods:
# Option 1: Target hostgroups
target_hostgroups:
- "All servers"
tasks:
- name: Create/remove maintenance window
community.zabbix.zabbix_maintenance:

18
roles/anubis/files/zabbix/template-anubis.yml
View file

@ -209,10 +209,10 @@ zabbix_export:
trigger_prototypes:
- uuid: 5f999d3911b84d7ca359ac4908eec6c1
expression: |
avg(/Anubis Monitoring/anubis.requests.rate[{#HOST}],5m) > 2 * avg(/Anubis Monitoring/anubis.requests.rate[{#HOST}],1h)
avg(/Anubis Monitoring/anubis.requests.rate[{#HOST}],5m) > 2 * avg(/Anubis Monitoring/anubis.requests.rate[{#HOST}],1h)
and
last(/Anubis Monitoring/anubis.requests.rate[{#HOST}]) > {$ANUBIS.MIN.REQUESTS}
name: 'Anomalous request rate for {#HOST} on {HOST.NAME}'
priority: AVERAGE
@ -261,7 +261,7 @@ zabbix_export:
- |
var metrics = JSON.parse(value);
var result = [];
metrics.forEach(function(metric) {
result.push({
"host": metric.labels.host,
@ -269,7 +269,7 @@ zabbix_export:
"low": metric.name < 100
});
});
return JSON.stringify(result);
- uuid: f33ad9b4b8e346d583245b9c429b48c6
name: 'Discover policies'
@ -314,9 +314,9 @@ zabbix_export:
- uuid: 8fd4921e126a4445991036f066f1e911
expression: |
avg(/Anubis Monitoring/anubis.policies.rate[{#POLICY},{#ACTION}],5m) > 2 * avg(/Anubis Monitoring/anubis.policies.rate[{#POLICY},{#ACTION}],1h)
and
last(/Anubis Monitoring/anubis.policies.rate[{#POLICY},{#ACTION}]) > {$ANUBIS.MIN.REQUESTS}
name: 'Anomalous request rate for {#ACTION}/{#POLICY} on {HOST.NAME}'
priority: AVERAGE
@ -367,7 +367,7 @@ zabbix_export:
- |
var metrics = JSON.parse(value);
var result = [];
metrics.forEach(function(metric) {
result.push({
"policy": metric.labels.rule,
@ -375,7 +375,7 @@ zabbix_export:
"metric": metric.name
});
});
return JSON.stringify(result);
macros:
- macro: '{$ANUBIS.MIN.REQUEST}'

18
roles/apache/files/zabbix/apache-template.yml
View file

@ -11,9 +11,9 @@ zabbix_export:
description: |
Get metrics from mod_status module using HTTP agent.
https://httpd.apache.org/docs/current/mod/mod_status.html
You can discuss this template or leave feedback on our forum https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/384764-discussion-thread-for-official-zabbix-template-apache
Generated by official Zabbix template tool "Templator"
vendor:
name: Zabbix
@ -457,33 +457,33 @@ zabbix_export:
'K': 0, 'D': 0, 'C': 0, 'L': 0,
'G': 0, 'I': 0, '.': 0
};
for (var i = 0; i < lines.length; i++) {
var line = lines[i].match(/([A-z0-9 ]+): (.*)/);
if (line !== null) {
output[line[1]] = isNaN(line[2]) ? line[2] : Number(line[2]);
}
}
output.ServerUptimeSeconds = output.ServerUptimeSeconds || output.Uptime;
output.ServerVersion = output.ServerVersion || output.Server;
if (typeof output.Scoreboard === 'string') {
for (var i = 0; i < output.Scoreboard.length; i++) {
var char = output.Scoreboard[i];
workers[char]++;
}
}
output.Workers = {
waiting: workers['_'], starting: workers['S'], reading: workers['R'],
sending: workers['W'], keepalive: workers['K'], dnslookup: workers['D'],
closing: workers['C'], logging: workers['L'], finishing: workers['G'],
cleanup: workers['I'], slot: workers['.']
};
return JSON.stringify(output);
tags:
- tag: component

2
roles/base/files/zabbix/base-template.yml
View file

@ -16,7 +16,7 @@ zabbix_export:
- Ping on it's BMC IP
- HTTP (80) on it's BMC IP
- HTTPS (443) on it's BMC IP
The BMC checks default to not triggering based on a macro which can be overridden from Ansible.
vendor:
name: Zabbix

6
roles/copr/backend/files/zabbix/template-copr-builds.yml
View file

@ -134,7 +134,7 @@ zabbix_export:
- uuid: 29fe2b0ea017407ea687196b47f21483
expression: |
(
last(/COPR Build metrics/copr.builds.last_attempt[{#POOL}]) - last(/COPR Build metrics/copr.builds.last_success[{#POOL}])
last(/COPR Build metrics/copr.builds.last_attempt[{#POOL}]) - last(/COPR Build metrics/copr.builds.last_success[{#POOL}])
) > {$COPR.LAST_SUCCESS.MAX_AGE:"{#POOL}"}
and
(
@ -154,7 +154,7 @@ zabbix_export:
- |
var metrics = JSON.parse(value);
var result = [];
Object.keys(metrics).forEach(function(pool) {
var metric = metrics[pool];
result.push({
@ -165,7 +165,7 @@ zabbix_export:
"{#STARTUP_AVG}": metric.startup_time_avg
});
});
return JSON.stringify(result);
tags:
- tag: not-infra

2
roles/copr/frontend/files/zabbix/template-copr-fe.yml
View file

@ -44,7 +44,7 @@ zabbix_export:
trends: '0'
description: |
'copr-be.aws.fedoraproject.org' is also apparently 'copr-be.cloud.fedoraproject.org' but both seem intermittent
Same for copr-be-dev.aws.fedoraproject.org too
preprocessing:
- type: CHECK_NOT_SUPPORTED

2
roles/dns/files/zabbix/template.yml
View file

@ -45,7 +45,7 @@ zabbix_export:
priority: HIGH
description: |
https://www.zabbix.com/documentation/7.0/en/manual/appendix/functions/history#find
returns 0 if string not found, so we test for 0. look for fedoraproject.org because some are internal (10.x) records and some are external (38.x) records
tags:
- tag: scope

2
roles/haproxy/files/zabbix/template-haproxy.yml
View file

@ -10,7 +10,7 @@ zabbix_export:
name: 'HAProxy Monitoring'
description: |
Imported & adapted from the upstream HAProxy template - https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/app/haproxy_agent
Current version: 1.0
vendor:
name: Zabbix

6
roles/ipa/botuser/tasks/main.yml
View file

@ -38,10 +38,10 @@
EOF
# We register and test to see if it's already there to keep it idempotent
register: ldap_out
failed_when:
- ldap_out.rc != 0
failed_when:
- ldap_out.rc != 0
- "'Type or value exists' not in ldap_out.stderr"
changed_when:
changed_when:
- ldap_out.rc == 0
tags:
- config

66
roles/ipatuura/tasks/main.yml
View file

@ -7,37 +7,37 @@
state: present
update_cache: yes
name:
- dbus-daemon
- dbus-devel
- gcc
- glib2-devel
- glibc
- httpd
- krb5-devel
- mod_ssl
- mod_wsgi
- openldap-devel
- openssl
- python3-devel
- python3-netifaces
- python3-pip
- python3-sssdconfig
- python-devel
- python-ipalib
- sssd-dbus
- unzip
- openldap-clients
- sssd
- sssd-ldap
- sssd-ipa
- realmd
- freeipa-client
- oddjob-mkhomedir
- mod_auth_gssapi
- mod_session
- gssproxy
- openssh-clients
- sshpass
- dbus-daemon
- dbus-devel
- gcc
- glib2-devel
- glibc
- httpd
- krb5-devel
- mod_ssl
- mod_wsgi
- openldap-devel
- openssl
- python3-devel
- python3-netifaces
- python3-pip
- python3-sssdconfig
- python-devel
- python-ipalib
- sssd-dbus
- unzip
- openldap-clients
- sssd
- sssd-ldap
- sssd-ipa
- realmd
- freeipa-client
- oddjob-mkhomedir
- mod_auth_gssapi
- mod_session
- gssproxy
- openssh-clients
- sshpass
# For psycopg2
- libpq-devel
tags:
@ -135,7 +135,7 @@
# mode: 0440
# tags:
# - ipatuura
#
#
# - name: Add Apache to the sssd group to edit the sssd.conf file
# ansible.builtin.user:
# name: apache
@ -411,7 +411,7 @@
# - Restart ipatuura
# tags:
# - ipatuura
#
#
# - name: Start the IPA-tuura container
# ansible.builtin.systemd:
# state: started

2
roles/openvpn/server/files/zabbix-template.yml
View file

@ -30,7 +30,7 @@ zabbix_export:
MONTHS_LIST = ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'],
month_index = ('0' + (MONTHS_LIST.indexOf(split[0]) + 1)).slice(-2),
ISOdate = split[3] + '-' + month_index + '-' + split[1] + 'T' + split[2];
return parseInt((Date.parse(ISOdate)) / 1000);
tags:
- tag: application

2
roles/packager_alias/tasks/main.yml
View file

@ -1,6 +1,6 @@
---
#
# This task sets up mail aliases scripts
# This task sets up mail aliases scripts
# It installs python packages, scripts and configure cron to run it.
#

32
roles/postgresql_server/files/zabbix/posgresql-template.yml
View file

@ -12,48 +12,48 @@ zabbix_export:
name: 'PostgreSQL by Zabbix agent active'
description: |
This template is designed for the deployment of PostgreSQL monitoring by Zabbix via Zabbix agent and uses user parameters to run SQL queries with the `psql` command-line tool.
Note:
- The template requires `pg_isready` and `psql` utilities to be installed on the same host with Zabbix agent.
- The template requires files with SQL queries and user parameters that can be found in the Zabbix official repository:
https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/db/postgresql?at=refs%2Fheads%2Frelease%2F6.0
Setup:
1. Deploy Zabbix agent and create the PostgreSQL user for monitoring (`<password>` at your discretion) with proper access rights to your PostgreSQL instance.
For PostgreSQL version 10 and above:
CREATE USER zbx_monitor WITH PASSWORD '<PASSWORD>' INHERIT;
GRANT pg_monitor TO zbx_monitor;
For PostgreSQL version 9.6 and below:
CREATE USER zbx_monitor WITH PASSWORD '<PASSWORD>';
GRANT SELECT ON pg_stat_database TO zbx_monitor;
ALTER USER zbx_monitor WITH SUPERUSER;
2. Copy the `postgresql/` directory to the `zabbix` user home directory - `/var/lib/zabbix/`. The `postgresql/` directory contains the files with SQL queries needed to obtain metrics from PostgreSQL instance.
If the home directory of the `zabbix` user doesn't exist, create it first:
mkdir -m u=rwx,g=rwx,o= -p /var/lib/zabbix
chown zabbix:zabbix /var/lib/zabbix
3. Copy the `template_db_postgresql.conf` file, containing user parameters, to the Zabbix agent configuration directory `/etc/zabbix/zabbix_agentd.d/` and restart Zabbix agent service.
If you want to use SSL/TLS encryption to protect communications with the remote PostgreSQL instance, you can modify the connection string in user parameters. For example, to enable required encryption in transport mode without identity checks you could append `?sslmode=required` to the end of the connection string for all keys that use `psql`:
UserParameter=pgsql.bgwriter[*], psql -qtAX postgresql://"$3":"$4"@"$1":"$2"/"$5"?sslmode=required -f "/var/lib/zabbix/postgresql/pgsql.bgwriter.sql"
Consult the PostgreSQL documentation about protection modes (https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION) and client connection parameters (https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-SSLMODE).
Also, it is assumed that you set up the PostgreSQL instance to work in the desired encryption mode. Check the PostgreSQL documentation (https://www.postgresql.org/docs/current/ssl-tcp.html) for details.
4. Edit the `pg_hba.conf` configuration file to allow connections for the user `zbx_monitor`. You can check the PostgreSQL documentation for examples (https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
5. Specify the host name or IP address in the `{$PG.HOST}` macro. Adjust the port number with `{$PG.PORT}` macro if needed.
6. Set the password that you specified in step 1 in the macro `{$PG.PASSWORD}`.
You can discuss this template or leave feedback on our forum https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/384190-%C2%A0discussion-thread-for-official-zabbix-template-db-postgresql
Generated by official Zabbix template tool "Templator"
vendor:
name: Zabbix

2
roles/rabbitmq_cluster/files/zabbix/template-rabbitmq-cluster.yml
View file

@ -11,7 +11,7 @@ zabbix_export:
description: |
This template is developed to monitor the messaging broker RabbitMQ cluster by Zabbix.
Most of the queue metrics are collected in one go, thanks to Zabbix bulk data collection.
The template collects queue metrics by running the get_queues script on the Zabbix agent.
The certificate expiration data is collected using the HTTP-accessible expiration JSON file, that a script on batcave produces.

18
roles/rabbitmq_cluster/files/zabbix/template-rabbitmq-node.stg.yml
View file

@ -11,26 +11,26 @@ zabbix_export:
description: |
This template is developed to monitor the messaging broker RabbitMQ node by Zabbix that works without any external scripts.
Most of the metrics are collected in one go, thanks to Zabbix bulk data collection.
The template collects metrics by polling RabbitMQ management plugin with HTTP agent remotely.
Setup:
1. Enable the RabbitMQ management plugin. See the RabbitMQ documentation for the instructions:
https://www.rabbitmq.com/management.html
2. Create a user to monitor the service:
rabbitmqctl add_user zbx_monitor <PASSWORD>
rabbitmqctl set_permissions -p / zbx_monitor "" "" ".*"
rabbitmqctl set_user_tags zbx_monitor monitoring
3. Set the hostname or IP address of the RabbitMQ node host in the '{$RABBITMQ.API.HOST}' macro. You can also change the port in the '{$RABBITMQ.API.PORT}' macro and the scheme in the '{$RABBITMQ.API.SCHEME}' macro if necessary.
4. Set the user name and password in the macros '{$RABBITMQ.API.USER}' and '{$RABBITMQ.API.PASSWORD}'.
You can discuss this template or leave feedback on our forum https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/387226-discussion-thread-for-official-zabbix-template-rabbitmq
Generated by official Zabbix template tool "Templator"
vendor:
name: Zabbix

18
roles/rabbitmq_cluster/files/zabbix/template-rabbitmq-node.yml
View file

@ -11,26 +11,26 @@ zabbix_export:
description: |
This template is developed to monitor the messaging broker RabbitMQ node by Zabbix that works without any external scripts.
Most of the metrics are collected in one go, thanks to Zabbix bulk data collection.
The template collects metrics by polling RabbitMQ management plugin with HTTP agent remotely.
Setup:
1. Enable the RabbitMQ management plugin. See the RabbitMQ documentation for the instructions:
https://www.rabbitmq.com/management.html
2. Create a user to monitor the service:
rabbitmqctl add_user zbx_monitor <PASSWORD>
rabbitmqctl set_permissions -p / zbx_monitor "" "" ".*"
rabbitmqctl set_user_tags zbx_monitor monitoring
3. Set the hostname or IP address of the RabbitMQ node host in the '{$RABBITMQ.API.HOST}' macro. You can also change the port in the '{$RABBITMQ.API.PORT}' macro and the scheme in the '{$RABBITMQ.API.SCHEME}' macro if necessary.
4. Set the user name and password in the macros '{$RABBITMQ.API.USER}' and '{$RABBITMQ.API.PASSWORD}'.
You can discuss this template or leave feedback on our forum https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/387226-discussion-thread-for-official-zabbix-template-rabbitmq
Generated by official Zabbix template tool "Templator"
vendor:
name: Zabbix

14
roles/varnish/files/zabbix/template.yml
View file

@ -10,14 +10,14 @@ zabbix_export:
name: 'Varnish Cache Monitoring'
description: |
## Description
Simple template for the Varnish cache using results from the varnishstat command.
Simple template for the Varnish cache using results from the varnishstat command.
## Overview
Simple template for the Varnish cache using results from the varnishstat command.
## Author: Greg Sutcliffe
Simple template for the Varnish cache using results from the varnishstat command.
## Author: Greg Sutcliffe
## Forked from: Dave Humphrey (dave@uesp.net)
groups:
- name: Fedora

2
roles/zabbix/datanommer/files/template-datanommer.yml
View file

@ -10,7 +10,7 @@ zabbix_export:
name: 'Datanommer Queue Times'
description: |
Times since the last message on a given queue.
Manually created for now, based on the Nagios config of old.
groups:
- name: Fedora

16
roles/zabbix/zabbix_server/files/templates/linux-by-zabbix-agent-active.yml
View file

@ -12,16 +12,16 @@ zabbix_export:
name: 'Linux by Zabbix agent active'
description: |
This is an official Linux template. It requires Zabbix agent 7.0 or newer.
Notes on filesystem (FS) discovery:
- The ext4/3/2 FS reserves space for privileged usage, typically set at 5% by default.
- BTRFS allocates a default of 10% of the volume for its own needs.
- To mitigate potential disasters, FS usage triggers are based on the maximum available space.
- Utilization formula: 'pused = 100 - 100 * (available / total - free + available)'
- The FS utilization chart, derived from graph prototypes, reflects FS reserved space as the difference between used and available space from the total volume.
You can discuss this template or leave feedback on our forum https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/387225-discussion-thread-for-official-zabbix-template-for-linux
Generated by official Zabbix template tool "Templator"
vendor:
name: Zabbix
@ -601,7 +601,7 @@ zabbix_export:
The available memory:
- in Linux = free + buffers + cache;
- on other platforms calculation may vary.
See also Appendixes in Zabbix Documentation about parameters of the `vm.memory.size` item.
tags:
- tag: component
@ -850,7 +850,7 @@ zabbix_export:
1. It can be triggered if the operations status is down.
2. `{$IFCONTROL:"{#IFNAME}"}=1` - a user can redefine the context macro to "0", marking this interface as not important. No new trigger will be fired if this interface is down.
3. `last(/TEMPLATE_NAME/METRIC,#1)<>last(/TEMPLATE_NAME/METRIC,#2)` - the trigger fires only if the operational status was up to (1) sometime before (so, does not fire for "eternal off" interfaces.)
WARNING: if closed manually - it will not fire again on the next poll, because of .diff.
manual_close: 'YES'
tags:
@ -866,7 +866,7 @@ zabbix_export:
description: |
It indicates the latest or current speed value of the interface. The value is an integer representing the link speed expressed in bits/sec.
This attribute is only valid for the interfaces that implement the ethtool `get_link_ksettings` method (mostly Ethernet).
Reference: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
preprocessing:
- type: MULTIPLIER
@ -1568,14 +1568,14 @@ zabbix_export:
parameters:
- |
var filesystems = JSON.parse(value);
result = filesystems.map(function (filesystem) {
return {
'fsname': filesystem.fsname,
'fstype': filesystem.fstype
};
});
return JSON.stringify(result);
- type: DISCARD_UNCHANGED_HEARTBEAT
parameters:

14
roles/zabbix/zabbix_server/files/templates/zabbix-server-health-by-zabbix-agent-active.yml
View file

@ -12,9 +12,9 @@ zabbix_export:
name: 'Zabbix server health by Zabbix agent active'
description: |
This template is designed to monitor Zabbix server metrics via the active Zabbix agent.
Specify the address of the remote Zabbix server by changing the {$ZABBIX.SERVER.ADDRESS} and {$ZABBIX.SERVER.PORT} macros. Don't forget to adjust the "StatsAllowedIP" parameter in the remote server's configuration file to allow the collection of statistics.
Generated by official Zabbix template tool "Templator"
vendor:
name: Zabbix
@ -2204,14 +2204,14 @@ zabbix_export:
parameters:
- |
var hacluster = JSON.parse(value);
result = hacluster.map(function (hanode) {
return {
'id': hanode.id,
'name': hanode.name
};
});
return JSON.stringify(result);
- type: DISCARD_UNCHANGED_HEARTBEAT
parameters:
@ -2255,7 +2255,7 @@ zabbix_export:
delay: '0'
description: |
Version of proxy compared to Zabbix server version.
Possible values:
0 - Undefined;
1 - Current version (proxy and server have the same major version);
@ -2554,14 +2554,14 @@ zabbix_export:
parameters:
- |
var proxies = JSON.parse(value);
result = proxies.map(function (proxy) {
return {
'name': proxy.name,
'proxy_group': proxy.proxy_group
};
});
return JSON.stringify(result);
- type: DISCARD_UNCHANGED_HEARTBEAT
parameters: