feat: trace dynamic config #617
Merged
Conversation
This file contains 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
sw1136562366
force-pushed
the
feat/trace_dynamic_config2
branch
from
305d6f0
to
a848233
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Closes #614
LINK Holoinsight Collector PR
Rationale for this change
The data flow is as follows：
trace_agent_configurationHoloinsight collector->(pull)->Holoinsight gateway->(pull)-> cache ->(pull)->tabletrace_agent_configurationThe trace agent configuration is added to the page and stored in the table
trace_agent_configuration, the gateway provides a configuration query interface to theholoinsight collector, theholoinsight gatewayhas a configuration cache, and the cache is updated every 30 seconds.What changes are included in this PR?
trace_agent_configuration_propertiesfor store the trace agent configuration metadatatrace_agent_configurationfor store the trace agent configuration from the pageAre there any user-facing changes?
How does this change test