You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/18 17:49:00 UTC
[jira] [Updated] (CASSANDRA-14347) Read payload metrics
[ https://issues.apache.org/jira/browse/CASSANDRA-14347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-14347:
-----------------------------------------
Component/s: Metrics
> Read payload metrics
> --------------------
>
> Key: CASSANDRA-14347
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14347
> Project: Cassandra
> Issue Type: Improvement
> Components: Metrics
> Reporter: Sumanth Pasupuleti
> Assignee: Sumanth Pasupuleti
> Priority: Major
> Fix For: 4.x
>
>
> We currently have MutationSizeHistogram that gives an idea of write payloads. This JIRA is about adding similar capability to reads, which can benefit us with the following
> * Histogram of payload sizes at Prepared Statement level
> * Count of queries that meet vs do not meet SLO w.r.t. payload size
> We could also log queries that result in payload exceeding SLO. This can prove useful in fire-fighting an incident, and can help resolve the issue since its easy to narrow down to the specific culprit prepared statement.
> Read payload metrics could potentially be derived using network statistics, however, it is difficult to isolate payloads due to reads, given that there could be a bunch of other operations in C* that can amount to observed network traffic (like repairs, streaming, etc).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org