Search before asking
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
Search before asking
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