[
https://issues.apache.org/jira/browse/KAFKA-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949223#comment-15949223
]
Edoardo Comar commented on KAFKA-4981:
--------------------------------------
Thanks I know the block is skipped for PLAINTEXT.
Actually we do not care that this rate is always 0 for PLAINTEXT - calling it
authenticated would work for us.
We wanted from an ops perspective to check how many requests go wasted either
because of failed TLS handshakes or failed authentications.
In fact this metric would be more useful if we add tags for the listener the
network thread belongs to
see https://issues.apache.org/jira/browse/KAFKA-4982
> Add connection-accept-rate and connection-prepare-rate metrics
> ---------------------------------------------------------------
>
> Key: KAFKA-4981
> URL: https://issues.apache.org/jira/browse/KAFKA-4981
> Project: Kafka
> Issue Type: Improvement
> Components: network
> Reporter: Edoardo Comar
> Assignee: Edoardo Comar
>
> The current set of socket-server-metrics include
> connection-close-rate and connection-creation-rate.
> On the server-side we'd find useful to have rates for
> connections accepted and connections 'prepared' (when the channel is ready)
> to see how many clients do not go through handshake or authentication
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
