ansible-role-prometheus-target/tasks, branch v1.1.0 Ansible role for pushing targets to prometheus instance Add ability to use exporter without id property 2023-06-15T20:52:07+00:00 Colin Wilk colin.wilk@tum.de 2023-06-15T20:40:27+00:00 579b168b2c93daee67ede17ee3289da1678b3833 The id property of the exporter is used for checking the default values specified in `prometheus_target_exporter_defaults` variable. However when both the `host` and the `path` fields are specified manually in the `prometheus_target_exporter` list this id is never looked up. The way the templating was handled however, still resulted in an error when leaving out the id field. The templating code was now rewritten to allow for the following exporter configuraion to run: prometheus_target_exporter: - { host: exporter_without_id, path: /opt/simple_target4.yml } Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
The id property of the exporter is used for checking the default values
specified in `prometheus_target_exporter_defaults` variable.
However when both the `host` and the `path` fields are specified
manually in the `prometheus_target_exporter` list this id is never
looked up.
The way the templating was handled however, still resulted in an error
when leaving out the id field.
The templating code was now rewritten to allow for the following
exporter configuraion to run:

prometheus_target_exporter:
- { host: exporter_without_id, path: /opt/simple_target4.yml }

Signed-off-by: Colin Wilk <colin.wilk@tum.de>
Add ability to specify target path prefix 2023-06-11T16:53:04+00:00 Colin Wilk colin.wilk@tum.de 2023-06-11T16:53:04+00:00 232bdca2add4253981b0873188663069f74a0610 This will decrease the amount of redundant configuration for users by allowing them to specify a general prefix on global / exporter / play level Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
This will decrease the amount of redundant configuration for users by
allowing them to specify a general prefix on global / exporter / play
level

Signed-off-by: Colin Wilk <colin.wilk@tum.de>
Add ability to configure default exporters 2023-05-30T16:38:12+00:00 Colin Wilk colin.wilk@tum.de 2023-05-30T16:37:11+00:00 139a3ebd76e6cb941776b03ead04c98f3a74b7f6 Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
Signed-off-by: Colin Wilk <colin.wilk@tum.de>
Rewrite if defined to default condition in lineinfile 2023-05-30T16:38:11+00:00 Colin Wilk colin.wilk@tum.de 2023-05-30T15:08:10+00:00 0b7dcb2fdda089009ac4afa4919b35479c9c4d41 Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
Signed-off-by: Colin Wilk <colin.wilk@tum.de>
Switch to single host per exporter configuration 2023-05-27T17:57:38+00:00 Colin Wilk colin.wilk@tum.de 2023-05-27T17:57:38+00:00 0b2823d40892ffca4c0c64536c6a821cebaf3ff6 Before you could do multiple hosts per exporter like this: - id: node_exporter hosts: - host1 - host2 This was removed since it simplifies the code quite a bit and you can still archive the same behavior like this: - { id: node_exporter, host: host1 } - { id: node_exporter, host: host2 } Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
Before you could do multiple hosts per exporter like this:

- id: node_exporter
  hosts:
    - host1
    - host2

This was removed since it simplifies the code quite a bit and you can
still archive the same behavior like this:

- { id: node_exporter, host: host1 }
- { id: node_exporter, host: host2 }

Signed-off-by: Colin Wilk <colin.wilk@tum.de>
init 2023-05-26T17:59:24+00:00 Colin Wilk colin.wilk@tum.de 2023-05-26T17:59:24+00:00 9db96602063e6ceb3cb8e819a8e942f28061bb42 Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
Signed-off-by: Colin Wilk <colin.wilk@tum.de>