You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Apoorv Mittal (Jira)" <ji...@apache.org> on 2024/09/18 21:12:00 UTC

[jira] [Created] (KAFKA-17577) May be record metrics on UnknownSubscriptionIdException

Apoorv Mittal created KAFKA-17577:
-------------------------------------

             Summary: May be record metrics on UnknownSubscriptionIdException
                 Key: KAFKA-17577
                 URL: https://issues.apache.org/jira/browse/KAFKA-17577
             Project: Kafka
          Issue Type: Sub-task
            Reporter: Apoorv Mittal
            Assignee: Apoorv Mittal


h3. Handling {{UnknownSubscriptionIdException}} (USIE)

When a broker changes telemetry subscriptions and a client attempts to report metrics with an outdated subscription ID, the broker throws {{UnknownSubscriptionIdException}} (USIE). In this case, the metrics payload is discarded, leading to a potential data gap.

If the client is using delta temporality (incremental metrics), this gap is reflected in external monitoring systems, which will observe a dip, potentially treating the next set of metrics as a new starting point. This can mislead monitoring systems and create inaccuracies.

The client should continue to work, as currently, by invoking {{GetTelemetrySubscriptionsRequest}} to renew the metrics subscription when broker throws {{{}USIE{}}}. However, the broker will record the telemetry metrics by validating the last subscription ID, reducing the chance of data gaps.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)