Page History

...

It will also be useful to know the time taken for down conversions. Fetch down conversion time metric will be a histogram in the same groupalongside other request time metrics. This time will also be included in request logs so that clients requiring expensive down conversions can be identified.

MBean: kafka.servernetwork:type=BrokerTopicMetricsRequestMetrics,name=FetchDownConversionsTimeMs,topic=([-.\w]+)request=Produce

Message batch size

Large messages can cause GC issues in the broker, especially if down conversions are required. Maximum message batch size can be configured per topic to control this, but that is the size after compression. Since the batches are decompressed to validate produce requests and for fetch downconversiondown conversion, it will be useful to have topic metrics for produce message batch size.

Topic Request metrics will be added for request size as well as the temporary memory size for processing the request. These two metrics will be histograms. For produce messages the two metrics will indicate message batch size before and after decompression as well as the compression ratio. The two sizes will give an indication of compression ratio as well. These two metrics will be histograms. values will also be included in request logs so that clients requiring a lot of temporary memory space can be identified.

MBean: kafka.servernetwork:type=BrokerTopicMetricsRequestMetrics,name=ProduceBatchSizeRequestSize,topic=([-.\w]+)request=<apiKey>

MBean: kafka.servernetwork:type=BrokerTopicMetricsRequestMetrics,name=ProduceUncompressedBatchSizeTemporaryMemorySize,topic=([-.\w]+)request=<apiKey>

Authentication success and failure rates

...