[
https://issues.apache.org/jira/browse/CASSANDRA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495166#comment-14495166
]
Matt Stump commented on CASSANDRA-9191:
---------------------------------------
Histograms don't provide the data granularity I'm looking for. I want the
actual statement. I was on a call today where I'm told "statements are failing
due to consistency failure" and I'm given no access to developers or access to
code. I'm ok with the feature being off by default as long as I can turn it on
via nodetool. Either that or give me the swiss army knife that is #9193.
> Log and count failure to obtain requested consistency
> -----------------------------------------------------
>
> Key: CASSANDRA-9191
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9191
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Matt Stump
>
> Cassandra should have a way to log failed requests due to failure to obtain
> requested consistency. This should be logged as error or warning by default.
> Also exposed should be a counter for the benefit of opscenter.
> Currently the only way to log this is at the client. Often the application
> and DB teams are separate and it's very difficult to obtain client logs. Also
> because it's only visible to the client no visibility is given to opscenter
> making it difficult for the field to track down or isolate systematic or node
> level errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
