charlesdong1991 opened a new issue, #3415: URL: https://github.com/apache/fluss/issues/3415
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Motivation ScannerMetricGroup scopes its metrics only by database and table, there is no per-scanner dimension. When two or more LogScanners run against the same database and table in the same client process, they all map to the same metric identity which could lead to wrong metric value to be reported. ### Solution Add a new dimension so concurrent scanners on the same table become distinct metric series, this will allow operators to alert with scenarios, e.g. something like `max by (database, table)`, where any stuck scanner will dominate and report that value for alerting for instance. ### Anything else? Happy to contribute if team thinks reasonable. ### Willingness to contribute - [x] I'm willing to submit a PR! -- 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]
