Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread Willem Jiang
I think we can start from the instance troubleshooting solution first, then we can consider to let management console redirect the request to the certain instance. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 5, 2019 at 11:54 AM wjm wjm wrote: > > @yaohai...@huawei.com agree

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread wjm wjm
@yaohai...@huawei.com agree to you. but 1.graphical user interface is not a problem, network is a problem browser maybe can not connect to the instance directly 2.we must provide these features by governance console, the problem is if we will provide it by instance also? when provide by gover

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread yhs0092
Here is just my personal consideration. It's indeed a complex problem when get involved in security issues. Once we decide this function is only provided directly by the service instances, users can only log into the micro-service clusters to get access to these informations. In such case we c

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread Willem Jiang
big +1 for providing a tool for user to do the trouble shoot. It could save us tons of time. For the swagger API documentation, my suggestion is we could provide a maven plugin to generate html file for it. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Mar 5, 2019 at 9:20 AM wjm wjm

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread wjm wjm
this feature should be for both development and production environment, so must conside security problem. currently i'm not sure what's the best way to control it. yhs0092 于2019年3月5日周二 上午10:28写道: > That's a great idea! > What is the positioning of this feature? If it's designed for development >

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread yhs0092
That's a great idea! What is the positioning of this feature? If it's designed for development environment trouble-shooting, I guess it's okay the web pages are provided by the micro-service instances directly. But if this feature is expected to work in production environment, which may contains

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread wjm wjm
@zhang_lei ServiceComb can run with spring boot, but will not depend on spring boot. wjm wjm 于2019年3月5日周二 上午9:49写道: > href of gif: > https://issues.apache.org/jira/secure/attachment/12961084/swaggerAndDocument.gif > and more question: > >- how to define the security of the new feature >-

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread wjm wjm
href of gif: https://issues.apache.org/jira/secure/attachment/12961084/swaggerAndDocument.gif and more question: - how to define the security of the new feature - should open a new port for the feature? wjm wjm 于2019年3月5日周二 上午9:20写道: > currently it's difficult to collect internal status

Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread zhang_...@boco.com.cn
Maybe you can customize it with spring boot actuator & metrics coolbeevip BOCO > 在 2019年3月5日,上午9:20,wjm wjm 写道: > > currently it's difficult to collect internal status of a microservice > instance when some problem happened. > eg: > routing depend on cached instanc

[discuss][java-chassis] new feature for inspect internal status of a microservice instance

2019-03-04 Thread wjm wjm
currently it's difficult to collect internal status of a microservice instance when some problem happened. eg: routing depend on cached instances, discovery tree, strategy of governances, and so on when we resolving routing related problem, we can only guess the status of all related modules.