Support configuring Monasca log pipeline performance
Change-Id: Id8948fcf2d165f8285c7562e7aebd4145c4ff0db Partially-Implements: blueprint monasca-roles
This commit is contained in:
parent
2b34f6d2fd
commit
01da938412
@ -64,6 +64,14 @@ monasca_metrics_topic: "metrics"
|
|||||||
monasca_raw_logs_topic: "logs"
|
monasca_raw_logs_topic: "logs"
|
||||||
monasca_transformed_logs_topic: "transformed-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
|
# Docker
|
||||||
####################
|
####################
|
||||||
|
Loading…
Reference in New Issue
Block a user