fix: adjust default producer/end-to-end latency buckets.

following #188, the default producer/end-to-end histogram buckets used by ihe canary are no longer ideal with all of the obseverations falling into the first (<=100ms) bucket. This change introduces several smaller buckets and drops the largest ones. Signed-off-by: kwall <kwall@apache.org>
strimzi · Jun 29, 2022 · ed20cee · ed20cee
1 parent 07a6ce3
commit ed20cee
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 4 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -4,6 +4,7 @@
 
 * Fixed replicas assignment taking rack configuration into account (#190)
 * Use separate sarama clients for producer/consumer in order to reliably measure message latency (#188)
+* Adjust default histogram bucket sizes (#194)
 
 ## 0.3.0
 

diff --git a/README.md b/README.md
@@ -62,8 +62,8 @@ The configuration file described in more detail the next section.
 | `RECONCILE_INTERVAL_MS` | It defines how often the tool has to send and receive messages (in ms). | `30000` |  |
 | `CLIENT_ID` | The client id used for configuring producer and consumer. | `strimzi-canary-client` |  |
 | `CONSUMER_GROUP_ID` | Group id for the consumer group joined by the canary consumer. | `strimzi-canary-group` |  |
-| `PRODUCER_LATENCY_BUCKETS` | Buckets of the histogram related to the producer latency metric (in ms). | `100,200,400,800,1600` |  |
-| `ENDTOEND_LATENCY_BUCKETS` | Buckets of the histogram related to the end to end latency metric between producer and consumer (in ms). | `100,200,400,800,1600` |  |
+| `PRODUCER_LATENCY_BUCKETS` | Buckets of the histogram related to the producer latency metric (in ms). | `2,5,10,20,50,100,200,400` |  |
+| `ENDTOEND_LATENCY_BUCKETS` | Buckets of the histogram related to the end to end latency metric between producer and consumer (in ms). | `5,10,20,50,100,200,400,800` |  |
 | `EXPECTED_CLUSTER_SIZE` | Expected number of brokers in the Kafka cluster where the canary connects to. This parameter avoids that the tool runs more partitions reassignment of the topic while the Kafka cluster is starting up and the brokers are coming one by one. `-1` means "dynamic" reassignment as described above. When greater than 0, the canary waits for the Kafka cluster having the expected number of brokers running before creating the topic and assigning the partitions | `-1` |  |
 | `KAFKA_VERSION` | Version of the Kafka cluster | `3.1.0` |  |
 | `SARAMA_LOG_ENABLED` | Enables the Sarama client logging. | `false` | `saramaLogEnabled` |

diff --git a/internal/config/canary_config.go b/internal/config/canary_config.go
@@ -57,8 +57,8 @@ const (
 	ReconcileIntervalDefault             = 30000
 	ClientIDDefault                      = "strimzi-canary-client"
 	ConsumerGroupIDDefault               = "strimzi-canary-group"
-	ProducerLatencyBucketsDefault        = "100,200,400,800,1600"
-	EndToEndLatencyBucketsDefault        = "100,200,400,800,1600"
+	ProducerLatencyBucketsDefault        = "2,5,10,20,50,100,200,400"
+	EndToEndLatencyBucketsDefault        = "5,10,20,50,100,200,400,800"
 	ExpectedClusterSizeDefault           = -1 // "dynamic" reassignment is enabled
 	KafkaVersionDefault                  = "3.1.0"
 	SaramaLogEnabledDefault              = false