diff --git a/checkstyle/suppressions.xml b/checkstyle/suppressions.xml index a111ce74cf660..4ce484dd2c747 100644 --- a/checkstyle/suppressions.xml +++ b/checkstyle/suppressions.xml @@ -213,7 +213,7 @@ + files="(RecordCollectorTest|StreamsPartitionAssignorTest|StreamThreadTest|StreamTaskTest|TaskManagerTest|TopologyTestDriverTest).java"/> diff --git a/docs/ops.html b/docs/ops.html index 843c5cc59e375..0c1973bd694a3 100644 --- a/docs/ops.html +++ b/docs/ops.html @@ -2308,7 +2308,7 @@

Streams Monitoring

A Kafka Streams instance contains all the producer and consumer metrics as well as additional metrics specific to Streams. - By default Kafka Streams has metrics with three recording levels: info, debug, and trace. + The metrics have three recording levels: info, debug, and trace.

Note that the metrics have a 4-layer hierarchy. At the top level there are client-level metrics for each started @@ -2617,7 +2617,7 @@

State Store Metrics
-All of the following metrics have a recording level of debug, except for the record-e2e-latency-* metrics which have a recording level trace>. +All of the following metrics have a recording level of debug, except for the record-e2e-latency-* metrics which have a recording level trace. Note that the store-scope value is specified in StoreSupplier#metricsScope() for user's customized state stores; for built-in state stores, currently we have: