poorbarcode opened a new pull request, #25583: URL: https://github.com/apache/pulsar/pull/25583
### Motivation Currently, in geo-replication scenarios, topic stats only clearly expose replicator information on the source cluster (e.g., Cluster A), while the destination cluster (Cluster B) lacks visibility into the origin of incoming traffic. For example: Cluster A: topic-1 → Cluster B: topic-1 On Cluster A, replicator stats are visible in topic stats. On Cluster B, there is no corresponding producer or replicator information shown. As a result, it is unclear where the incoming traffic (input rate) is coming from. This is because replicator producers are intentionally filtered out on the destination cluster side. However, this leads to poor observability, as users cannot determine the source of incoming data from topic stats alone. ### Modifications Fix the issue ### Does this pull request potentially affect one of the following parts: - [ ] Dependencies (add or upgrade a dependency) - [ ] The public API - [ ] The schema - [ ] The default values of configurations - [ ] The threading model - [ ] The binary protocol - [ ] The REST endpoints - [ ] The admin CLI options - [ ] The metrics - [ ] Anything that affects deployment -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
