9c2e0b81d5
On a single node deployment, the Monasca persister can limit the rate at which Monasca can persist metrics to InfluxDB. Increasing the thread count can remove this bottle neck. Partially-Implements: blueprint monasca-roles Change-Id: I763a5ae6aa8c8ab3bf766ab5b58c386da74a188b
24 lines
648 B
Django/Jinja
24 lines
648 B
Django/Jinja
[DEFAULT]
|
|
log_file = monasca-persister.log
|
|
log_dir = /var/log/kolla/monasca
|
|
debug = {{ monasca_logging_debug }}
|
|
|
|
[influxdb]
|
|
database_name = {{ monasca_influxdb_name }}
|
|
# FIXME(dszumski): This doesn't work with a FQDN so use the VIP directly
|
|
ip_address = {{ kolla_internal_vip_address }}
|
|
port = {{ monasca_influxdb_http_port }}
|
|
|
|
[kafka_alarm_history]
|
|
uri = {{ monasca_kafka_servers }}
|
|
topic = {{ monasca_alarm_state_transitions_topic }}
|
|
num_processors = 1
|
|
|
|
[kafka_metrics]
|
|
uri = {{ monasca_kafka_servers }}
|
|
topic = {{ monasca_metrics_topic }}
|
|
num_processors = {{ monasca_metric_pipeline_threads }}
|
|
|
|
[zookeeper]
|
|
uri = {{ monasca_zookeeper_servers }}
|