Re: LogViewer Basic Question

[Joaquin Menchaca <jm...@gobalto.com>]

Thank you.  I'll look into this, doing a PR.

Once I figured out how it worked, it was pretty simple, but I have
another issue, in how links are created, using private DNS names.   I
would like to chose what the links should be for my supervisor
systems.  Currently, it defaults to private AWS names, but this
doesn't work if I should chose to a front reverse proxy server.

Is there any way to control what the link looks like?

On Wed, Aug 31, 2016 at 12:52 AM, Jungtaek Lim <ka...@gmail.com> wrote:
> UI just creates the link based on the informations which are retrieved from
> Nimbus. No request on supervisor to get logviewer's link.
> In other words, UI assumes that logviewers are running for each supervisor
> node. If Nimbus is running on another nodes logviewer should also be
> launched there.
>
> I sought some documentations for 1.0.2, and found logviewer on "Command Line
> Client" but no luck on "Setting up a Storm Cluster". Logviewer should also
> be in "Setting up a Storm Cluster".
>
> I can take care of it, but if you really don't mind, you can submit a pull
> request updating this doc.
> Please let me know if you would like to provide one.
>
> Thanks,
> Jungtaek Lim (HeartSaVioR)
>
>
> 2016년 8월 31일 (수) 오전 8:40, Joaquin Menchaca <jm...@gobalto.com>님이 작성:
>>
>> The logviewer service should be run on each of the supervisors?  Then
>> the ui service connects to the supervisors?
>>
>> I just want to make sure.
>>
>> I combed through the documentation and it is sparse.  There was a
>> release note on it in 0.9.x, and it is not documented in the command
>> line interface for any version into 1.x.  And even then, it specified
>> a link for configuration of this service, which leads to more lack of
>> documentation, only specifying something about plug-ins, but nothing
>> how to set this up.
>>
>> --
>>
>> 是故勝兵先勝而後求戰，敗兵先戰而後求勝。



-- 

是故勝兵先勝而後求戰，敗兵先戰而後求勝。