I think you totally understand the documentation in the wrong way. That is
the thing I am confused about.
The document says nothing about these keys are in the application.yml, and
the dynamic configuration has nothing related to it

>  SkyWalking Configurations mostly are set through application.yml and OS
system environment variables. But some of them are supporting dynamic
settings from upstream management system.
This is background, about what you are using default.

If this thing is very hard for you to understand, I would recommend you to
read some codes, such as all implementations of DynamicConfigurationService
Dynamic Configuration is a very common, widely used thing, it is SkyWalking
keeps watching someplace through config server(zookeeper, etcd...) or grpc.
Those things provide the change notification.
Then, OAP interacts based on their response. That is all.

Sheng Wu 吴晟
Twitter, wusheng1108


Benchu Yao <[email protected]> 于2020年6月3日周三 下午5:27写道:

> I don't understand the documentation
>
> My understanding of the documentation is:.
> first:configure alarm.default. alarm-settings
> alarm:
>     selector: ${SW_ALARM:default}
>     default:
>         alarm-settings:What should I fill in here?There is no
> alarm-settings example in the current version of application.yml.Maybe
> nothing is needed.
>
> second:configure  SW_CONFIGURATION
>
> configuration:
>   selector: ${SW_CONFIGURATION:grpc}
>   none:
>   grpc:
>     host: ${SW_DCS_SERVER_HOST:"my host"}
>     port: ${SW_DCS_SERVER_PORT:80}
>     clusterName: ${SW_DCS_CLUSTER_NAME:SkyWalking}
>     period: ${SW_DCS_PERIOD:20}
>
>
> third:oap fetches data from my grpc service through grpc protocol, the data
> format is the same as alarm-settings.yml
>
>
> I think my understanding should be wrong, but I did not understand the
> documentation.
>  Is the dynamic configuration available in the newly released skywalking
> version?
>  I only found slowDBAccessThreshold in application.yml, but none of the
> other four.
>
>
> Thanks,
>
> Yao Benchu
>
>
>
> Sheng Wu <[email protected]> 于2020年6月3日周三 下午2:13写道:
>
> > I am confused, do you read the document? It is very clear there.
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> >
> > Benchu Yao <[email protected]> 于2020年6月3日周三 下午1:54写道:
> >
> > > Does it mean that I implement a third-party tool and then
> skywalking-oap
> > > fetches the configuration from my tool?
> > >
> > > If so, what are the restrictions for the data structure of third-party
> > > tools
> > >
> > > Sheng Wu <[email protected]> 于2020年6月3日周三 上午11:19写道:
> > >
> > > > Upstream management system is the 3rd party system, anything you
> like.
> > > > We provide watching or grpc sync mechanism. So, you could choose how
> > you
> > > > could change the setting.
> > > >
> > > > Where depends on your choice.
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > >
> > > > Benchu Yao <[email protected]> 于2020年6月3日周三 上午11:05写道:
> > > >
> > > > > How to configure alarms dynamically
> > > > >
> > > > > What is the upstream management system in the document
> > > > > <
> > > > >
> > > >
> > >
> >
> https://github.com/apache/skywalking/blob/8af10bed11d0eac53e8eab13a3df276cd613647d/docs/en/setup/backend/dynamic-config.md
> > > > > >
> > > > >  ?
> > > > >
> > > > > Where is Config Key configured?
> > > > >
> > > > >
> > > > >
> > > > > Thanks,
> > > > > Yao Benchu
> > > > >
> > > >
> > >
> >
>

Reply via email to