[
https://issues.apache.org/jira/browse/KAFKA-19969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandini Singhal reassigned KAFKA-19969:
---------------------------------------
Assignee: Nandini Singhal
> Add Per-Topic Observability Metrics for Remote Fetch Quota Enforcement
> ----------------------------------------------------------------------
>
> Key: KAFKA-19969
> URL: https://issues.apache.org/jira/browse/KAFKA-19969
> Project: Kafka
> Issue Type: Task
> Components: Tiered-Storage
> Reporter: Nandini Singhal
> Assignee: Nandini Singhal
> Priority: Major
>
> The current tiered storage quota implementation provides only broker-level
> metrics for remote fetch quota monitoring. While per-topic metrics exist for
> basic remote fetch operations, there are no per-topic metrics for quota
> consumption and throttling behavior.
> This creates a blind spot when:
> - Multiple topics use tiered storage on the same broker
> - Operators need to identify which topics are consuming quota
> - Debugging why certain topics are being throttled
> - Planning quota allocation across topics
> - Implementing topic-level SLAs for remote storage performance
>
> Add the following per-topic metrics
> # RemoteFetchQuotaBytesPerSec
> # RemoteFetchQuotaThrottledRequestsPerSec
> # RemoteFetchQuotaThrottleTimeMs
> # RemoteFetchSizeBytes
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
