openstack/kolla-ansible
Code Issues Proposed changes

Support configuring prometheus fetcher for CloudKitty

Browse Source 
Change-Id: I7d79a18599f54583ff4f38a554459fe02ada9ae7
This commit is contained in:
Pierre Riteau 2022-07-08 12:34:40 +02:00
parent 3058b5bcd7
commit 2b5cef68d7
2 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
ansible/roles/cloudkitty/templates/cloudkitty.conf.j2
View File

@ -89,6 +89,19 @@ auth_section = keystone_authtoken
region_name = {{ openstack_region_name }}
{% endif %}
{% if cloudkitty_fetcher_backend == "prometheus" %}
[fetcher_prometheus]
metric = openstack_identity_project_info
scope_attribute = id
prometheus_url = {{ cloudkitty_prometheus_url }}
{% if cloudkitty_prometheus_cafile is defined %}
cafile = {{ cloudkitty_prometheus_cafile }}
{% endif %}
insecure = {{ cloudkitty_prometheus_insecure_connections }}
{% endif %}
[api]
host_ip = {{ api_interface_address }}
port = {{ cloudkitty_api_port }}

6
doc/source/reference/rating/cloudkitty-guide.rst
View File

@ -59,7 +59,11 @@ CloudKitty natively supports multiple fetcher backends.
By default Kolla Ansible uses the ``keystone`` backend. This can be changed
using the ``cloudkitty_fetcher_backend`` option.
You will need to provide extra configuration for non-default fetchers in
Kolla Ansible also supports the ``prometheus`` backend type, which is
configured to discover scopes from the ``id`` label of the
``openstack_identity_project_info`` metric of OpenStack exporter.
You will need to provide extra configuration for unsupported fetchers in
``/etc/kolla/config/cloudkitty.conf``.
Cloudkitty Storage Backend