You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/07/11 19:00:00 UTC
[jira] [Commented] (KUDU-2497) Add a metric for the number of
unauthenticated connection attempts
[ https://issues.apache.org/jira/browse/KUDU-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540533#comment-16540533 ]
Todd Lipcon commented on KUDU-2497:
-----------------------------------
In addition, are the existing logs relatively clear about the type of unauthenticated connection? eg do we differentiate between "client had no creds at all" vs "client had an authn token that was expired"? Would be good to separate out the metric by type as well.
> Add a metric for the number of unauthenticated connection attempts
> ------------------------------------------------------------------
>
> Key: KUDU-2497
> URL: https://issues.apache.org/jira/browse/KUDU-2497
> Project: Kudu
> Issue Type: Improvement
> Components: security, server
> Reporter: Andrew Wong
> Priority: Major
>
> When a client's authentication token expires, upon connecting to a master or tserver, the result is that the Kudu server logs a warning message about an unauthenticated connection attempt. It would be nice if these connections were quantified as a metric instead, particularly in cases where there are a large number of these messages.
> Note: this would be particularly helpful when users are using older versions of the Java client, that may not reauthenticate automatically, leading to a huge amount of warning messages in the logs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)