[FLUSS-3415][client] Add per-scanner dimension for scanner metrics#3534
Open
Jackeyzhe wants to merge 1 commit into
Open
[FLUSS-3415][client] Add per-scanner dimension for scanner metrics#3534Jackeyzhe wants to merge 1 commit into
Jackeyzhe wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Linked issue: close #3415
Brief change log
Add scanner_id in ScannerMetricGroup, make sure when two or more LogScanners run against the same database and table in the same client process, client could report right metric value.
Tests
Add
TestingScannerMetricGroup.testScannerMetricGroupContainsScannerIdDimensionAPI and Format
no
Documentation
no