Monasca removal followup
A few minor fixes were noted in this review [1], and they are addressed here. TrivialFix [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/861392/ Change-Id: If30d9c2b48615dfb54edcb8d782c4c24b968ac4b
This commit is contained in:
parent
8f6298c845
commit
04d3bb3666
@ -33,7 +33,7 @@
|
||||
|
||||
# Rename internal Fluent message field to match other logs. This removes
|
||||
# all other fields by default, including the original message field. This is
|
||||
# intented to avoid duplication of the log message. Note that if this step
|
||||
# intended to avoid duplication of the log message. Note that if this step
|
||||
# is moved to the format folder, then it will applied after the second step
|
||||
# below which will break the logic.
|
||||
<filter fluent.**>
|
||||
|
@ -29,10 +29,8 @@ CloudKitty Collector backend
|
||||
|
||||
CloudKitty natively supports multiple collector backends.
|
||||
|
||||
By default Kolla Ansible uses the Gnocchi backend,
|
||||
however we also support using the following backend types:
|
||||
|
||||
- ``prometheus`` - Use Prometheus metrics as dataset for cloudkitty to process.
|
||||
By default Kolla Ansible uses the Gnocchi backend. Using data
|
||||
collected by Prometheus is also supported.
|
||||
|
||||
The configuration parameter related to this option is
|
||||
``cloudkitty_collector_backend``.
|
||||
|
Loading…
Reference in New Issue
Block a user