executor/inspect: Add a status_address
of inspection_result
table…
#17695
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.
Signed-off-by: crazycs520 crazycs520@gmail.com
cherry-pick #15589
Fix pingcap/tidb-dashboard#586
What problem does this PR solve?
Before this PR, the
instance
value ofinspection_result
is wrong. The value in some row isgrpc service address
, such as127.0.0.1:4000
, the value in some row isstatus address
, such as127.0.0.1:10080
.instance
value.status_address
ofinspection_result
table to indicate thestatus address
.Why add a
status_address
?Because some diagnose rule such as
server down
, we can only get thestatus address
from Prometheus.Check List
Tests
Side effects
Release note
status_address
ofinspection_result
table to indicate thestatus address
.