DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| Kafka Streams metric name | Telemetry metric name |
|---|---|
| "process-records-avg, group=stream-thread-metrics" | "org.apache.kafka.stream.thread.process.records.avg" |
| "commit-latency-max, group=stream-thread-metrics" | "org.apache.kafka.stream.thread.commit.latency.max" |
Metric format
Since this proposed KIP is an extension of KIP-714, it will follow the same approach for supported metric types. When providing metrics via registerMetricsForSubscription, only metrics of type sum (a monotonic counter, like process-total) and gauge (a non-monotonic value, like process-rate) are registered, other types are dropped generating a log WARN statement.
Configuration
With KIP-714, clients use the ENABLE_METRICS_PUSH_CONFIG configuration to enable pushing metrics. Kafka Streams also has the ENABLE_METRICS_PUSH_CONFIG configuration, which is meant to extend to the internal client's ability to push metrics.
...
It's important to note that since Kafka Streams leverages the client metrics mechanism, disabling metrics for internal clients removes the possibility of pushing Kafka Streams metrics. In practice, this is not an anticipated scenario, but in the interest of completeness, it's worth specifying it here in the KIP
To alert the user to this significant configuration mismatch, a Kafka Streams application configured with ENABLE_METRICS_PUSH_CONFIG=true and a main or admin consumer configured with ENABLE_METRICS_PUSH_CONFIG=false, will result in ConfigException on start-up.
Compatibility, Deprecation, and Migration Plan
...