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 <zzz...@gmail.com> wrote: > 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. > > so we should provide a way to inspect the internal status of a > microservice instance at runtime, maybe include: > > - discovery tree > - isolation > - eventbus > - view schemas as swagger or html/pdf...... > - ...... > > maybe like the gif: > [image: swaggerAndDocument.gif] > > my question: > > - provide these informations include related html/js/css by instance > directly, or only by governance console > > if provide by both instance and governance console, that will > cause duplicate development > > - if provide by instance > - what's the name of the module? "inspector"? > - swagger to html depend on "asciidoctor", which depend on jruby, > it's very heavy. > - in my demo, resource of swagger and asciidoctor all load from > cdn, but for some customer's environment, maybe can not connect to > internet. > - any other idea? > >
