From 01da93841233fb5a25862fb8020755f59d7826e2 Mon Sep 17 00:00:00 2001
From: Doug Szumski <doug@stackhpc.com>
Date: Tue, 25 Sep 2018 11:07:22 +0000
Subject: [PATCH] Support configuring Monasca log pipeline performance

Change-Id: Id8948fcf2d165f8285c7562e7aebd4145c4ff0db
Partially-Implements: blueprint monasca-roles
---
 ansible/roles/monasca/defaults/main.yml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/ansible/roles/monasca/defaults/main.yml b/ansible/roles/monasca/defaults/main.yml
index 0c8b717f0e..55c2f125dc 100644
--- a/ansible/roles/monasca/defaults/main.yml
+++ b/ansible/roles/monasca/defaults/main.yml
@@ -64,6 +64,14 @@ monasca_metrics_topic: "metrics"
 monasca_raw_logs_topic: "logs"
 monasca_transformed_logs_topic: "transformed-logs"
 
+# Processing pipeline threads. In a large scale deployment you will likely
+# want to tune these with finer precision. For example, if you have a very
+# high log throughput, the log metrics service consumer may require a
+# higher thread count than the producer. You will also want to ensure that
+# the total number of threads across all instances of a service does not
+# exceed the Kafka topic partition count.
+monasca_log_pipeline_threads: 2
+
 ####################
 # Docker
 ####################