RockteMQ-AI commented on issue #11078: URL: https://github.com/apache/rocketmq/issues/11078#issuecomment-5711089183
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** This is a reasonable enhancement request to support suppressing minimal-value metrics to reduce export payload. **Feasibility:** Feasible - can be implemented as a configurable threshold filter in the metrics export pipeline. **Scope:** Metrics collection and export subsystem. Affects all metric exporters (Prometheus, OpenTelemetry, etc.). **Compatibility:** No breaking changes expected. Should be opt-in via configuration to preserve existing behavior. **Assessment:** This is a valuable optimization for large-scale deployments where metrics cardinality can impact monitoring system performance. The implementation should: 1. Add a configurable threshold (e.g., `metrics.min.value.threshold`) 2. Apply filtering at the export stage, not collection stage 3. Preserve all metrics when threshold is not configured (default behavior) This would benefit operations teams running large RocketMQ clusters with high metric cardinality. --- *Automated evaluation by RockteMQ-AI* -- 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]
