文件列表:

LICENSE.md (1306, 2023-10-26)
defaults/ (0, 2023-10-26)
defaults/main.yml (2191, 2023-10-26)
files/ (0, 2023-10-26)
files/etc-prometheus-blackbox-exporter.yml (526, 2023-10-26)
meta/ (0, 2023-10-26)
meta/main.yml (305, 2023-10-26)
molecule/ (0, 2023-10-26)
molecule/default/ (0, 2023-10-26)
molecule/default/Dockerfile.j2 (961, 2023-10-26)
molecule/default/example-rules-yml.j2 (673, 2023-10-26)
molecule/default/molecule.yml (857, 2023-10-26)
molecule/default/playbook.yml (1849, 2023-10-26)
molecule/default/requirements.yml (50, 2023-10-26)
molecule/default/tests/ (0, 2023-10-26)
molecule/default/tests/test_defaults.py (2181, 2023-10-26)
tasks/ (0, 2023-10-26)
tasks/main.yml (6616, 2023-10-26)
templates/ (0, 2023-10-26)
templates/etc-prometheus-additional-alert-rules-yml.j2 (134, 2023-10-26)
templates/etc-prometheus-alertmanager-yml.j2 (2435, 2023-10-26)
templates/etc-prometheus-default-alert-rules-yml.j2 (1004, 2023-10-26)
templates/etc-prometheus-prometheus-yml.j2 (4402, 2023-10-26)
templates/file_sd_config-template-yml.j2 (559, 2023-10-26)

Prometheus ========== [](https://github.com/ome/ansible-role-prometheus/actions) [](https://galaxy.ansible.com/ui/standalone/roles/ome/prometheus/) Prometheus monitoring server, includes prometheus, alertmanager and blackbox-exporter. This requires docker to be running (not handled by this role). This role is still in development. Parameters ---------- - `prometheus_targets`: Optional list of dictionaries of targets: - `group`: A list of Ansible groups (optional) - `hosts`: A list of hosts (optional) - `port`: The port to be monitored - `jobname`: The prometheus job-name - `scrape_interval`: Prometheus scrape interval (optional) - `metrics_path`: Path to metrics (optional) - `prometheus_sd_targets`: Optional list of dictionaries of additional targets: - `groupname`: The name of the configuration target file, used to name a configuration file so must be unique - `group`: A list of Ansible groups (optional) - `hosts`: A list of hosts (optional) - `port`: The port to be monitored - `jobname`: The prometheus job-name This is intended to be an example. In practice these configuration files could be dynamically generated outside this role, prometheus will automatically reload them. - `prometheus_custom_targets`: Optional list of dictionaries of additional targets with custom arguments, use this if you need to pass custom arguments that aren't supported by the previous two parameters. Each item is a [``](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config) that will be copied unchanged into the configuration. - `prometheus_port`: External Prometheus port, set to `0` to disable, default `9090` - `prometheus_alertmanager_port`: External Alertmanager port, set to `0` to disable, default `9093` - `prometheus_blackboxexporter_port`: External Blackbox-exporter port, set to `0` to disable, default `9115` - `prometheus_additional_command_args`: Additional command line arguments for prometheus - `prometheus_alertmanager_additional_command_args`: Additional command line arguments for alertmanager - `prometheus_additional_rules_template`: Template with additional alert rules. See https://awesome-prometheus-alerts.grep.to/rules for some ideas but note the labels may be different. - `prometheus_docker_network`: Docker network for prometheus Docker applications, default `prometheus` - `prometheus_docker_user`: User ID that prometheus should run as, default is the container default - `prometheus_docker_data_volume`: Docker volume or host path for Prometheus data, default is a docker volume called `prometheus-data`. If this is a host path it must be writeable by `prometheus_docker_user`. Outputs ------- This role sets the following variables which can be used in other tasks: - `prometheus_internal_ip`: Internal IP of the Prometheus container - `prometheus_blackboxexporter_internal_ip`: Internal IP of the Blackbox exporter container - `prometheus_alertmanager_internal_ip`: Internal IP of the AlertManager container These are intended for use when you don't want to expose the container ports using standard Docker port-forwarding (set `prometheus_*port: 0`). Example playbook ---------------- - hosts: localhost roles: - role: ome.docker - role: ome.prometheus Testing Slack alerts (manual) ----------------------------- Change `prometheus_alertmanager_slack_webhook` in `playbook.yml` to a real Slack webhook. Run: molecule test --destroy never molecule login docker stop fake-metrics Wait a few minutes, a Slack alert should be generated. If this fails try creating a [manual alert](https://github.com/prometheus/alertmanager/issues/437#issuecomment-263413632): curl -H "Content-Type: application/json" -d '[{"labels":{"alertname":"TestAlert1"}}]' localhost:9093/api/v1/alerts The molecule test also includes a disk space alert configuration. To test this fill up at least 90% of the `/run` partition: molecule login dd if=/dev/zero of=/run/fill.space bs=1M count=... Wait a few minutes and you should see a disk space warning. Author Information ------------------ ome-devel@lists.openmicroscopy.org.uk

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：