[
https://issues.apache.org/jira/browse/CASSANDRA-17062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747278#comment-17747278
]
Sam Tunnicliffe commented on CASSANDRA-17062:
---------------------------------------------
[~smiklosovic] I'm afraid I haven't given this much (any) thought for quite
some time, but my instinctive reaction is that increasing the scope is only
likely to further delay this, so I'd probably suggest a follow up JIRA.
I'm going to be afk for the next couple of weeks and beyond that I'm pretty
much tied up with getting CEP-21 into shape for 5.0 so I don't expect I'll have
a lot of spare cycles for this (just fyi, so I don't block you on it).
> Expose Auth Caches metrics
> --------------------------
>
> Key: CASSANDRA-17062
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17062
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Virtual Tables, Observability/Metrics,
> Tool/nodetool
> Reporter: Aleksei Zotov
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
>
> Unlike to other caches (row, key, counter), Auth Caches lack some monitoring
> capabilities. Here are a few particular changes to get this inequity fixed:
> # Add auth caches to _system_views.caches_ VT
> # Expose auth caches metrics via JMX
> # Add auth caches details to _nodetool info_
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
