fix(skywalking): start timer when route is hit #12855
Open
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.
Description
When skywalking is enabled but
plugin_attris not configured, the default skywalkingendpoint_addris taken into affect and error logs may be continuously printed as that endpoing may not be available by default. This behaviour is annoying and unnecessary.So this PR introduces a change that starts the timer that performs reporting only after a route configuring
skywalkingplugin is hit instead of starting it directly when the plugin is initialised during startup.Checklist