君浩 <[email protected]> 于2019年11月27日周三 下午4:00写道：
> Hi, all: > Personally, I think add prometheus to SW is another feature, it's > meaningful and important. But should not contained in our operator. As > prometheus has it's operator too. > Gao This makes sense to me Sheng Wu 吴晟 Twitter, wusheng1108 > We should keep our operator functionality simple and scalable and stable. > After all, the operator exists to simplify the use of SW in K8S and > automate some common tasks. > > > Sheng Wu <[email protected]> 于2019年11月26日周二 下午4:58写道： > > > Personally, Prometheus makes more sense to me. Self-obs seems not > powerful > > enough yet. > > > > > Cons: > > OAP didn't store dynamic metrics except for the items related to three > > scopes(service, service_instance, and endpoint) > > > > For this, I think we should have separated discussion about this, I am > > thinking about this for a while, service, and service_instance are not > the > > issue, don't support extension for this is the root cause. > > Such as, if we have 3rd service level extension metrics, with tag name > and > > value, then OAL and the currently existing system design still works. > > We should have a separated thread to discuss this. > > > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > > > > > Hongtao Gao <[email protected]> 于2019年11月26日周二 下午4:22写道： > > > > > That's another problem I didn't have the answer. At this point we have > > two > > > choices for it: > > > 1. OAP self-observability module with telemetry module. > > > Pros: > > > It's our project, and we have the experience and abilities to do > > > whatever we want. > > > Cons: > > > OAP didn't store dynamic metrics except for the items related to > three > > > scopes(service, service_instance, and endpoint) > > > 2. Prometheus with telemetry module. > > > Pros: > > > It can store any metrics we want. > > > Cons: > > > it brings some performance overhead, especially to complete a > minimal > > > deployment. > > > > > > So what's your suggestion? > > > > > > 付金林 Jinlin Fu <[email protected]> 于2019年11月26日周二 上午11:01写道： > > > > > > > what do you think should be contain prometheus in operator? > > > > > > > > 付金林 Jinlin Fu <[email protected]> 于2019年11月26日周二 上午10:51写道： > > > > > > > > > Hi > > > > > > > > > > If using webhook in SWCK project,i recommend using > kubebuilder,which > > it > > > > > can automatically generate the webhook code.also operator-sdk does > > not > > > > do > > > > > it. > > > > > > > > > > > > > > > Hongtao Gao <[email protected]> 于2019年11月26日周二 上午10:04写道： > > > > > > > > > >> Hi everyone > > > > >> > > > > >> I'm glad to share my proposal with you about to setup SkyWalking > > Cloud > > > > on > > > > >> Kubernetes(SWCK) project. > > > > >> > > > > >> The aim of SWCK is to enable users to configure and manage > instances > > > of > > > > >> SkyWalking components using a simple declarative configuration > that > > > > will, > > > > >> in response, create, configure, and manage those components. > > > > >> > > > > >> The following is the doc of this proposal. I'm hoping to hear > > thoughts > > > > >> from > > > > >> you soon. > > > > >> > > > > >> [PROPOSAL]SkyWalking Cloud on Kubernetes(SWCK) - > > > > >> > > > > >> > > > > > > > > > > https://docs.google.com/document/d/1tPv3ppjNEMa5frX2qRzUXVNky4U4TuTr8qzaiU2wpso/edit?usp=sharing > > > > >> > > > > >> > > > > >> ------ > > > > >> Hongtao Gao > > > > >> > > > > >> Apache SkyWalking && Apache ShardingSphere > > > > >> Twitter, @hanahmily > > > > >> > > > > > > > > > > > > > > > -- > > > > > *Jinlin Fu* > > > > > > > > > > > > > > > > > -- > > > > *Jinlin Fu* > > > > > > > > > > > > > -- > > > Hongtao Gao > > > > > > Apache SkyWalking && Apache ShardingSphere > > > Twitter, @hanahmily > > > > > >
