> >> > >>>> We're working with this here at work as well, so implementing
> >> at
> >> > >>> least a
> >> > >>>> first MVP might be feasible as well, before getting to deep
> >> into
> >> > A1
> >> > >>>> spe
> >>>>
>> > >>>> --
>> > >>>>
>> > >>>>
>> > >>>> *Fabian WollertZalando SE*
>> > >>>>
>> > >>>> E-Mail: fab...@zalando.de
>> > >>>>
>>
t;> rmetz...@apache.org>:
> > >>>>
> > >>>>> Hey Fabian,
> > >>>>> thanks a lot for reaching out to the Flink community with this
> > >>> proposal!
> > >>>>> (Posting to the ML instead of creating a JIRA is a good idea for
> such
> > >>>>
>> has
> >>>>> come to a conclusion)
> >>>>>
> >>>>> I have two comments:
> >>>>> - You are listing Records/Kb in and Records/Kb out as cluster-wide
> >>>> metrics.
> >>>>> I wonder whether we should rather show these metrics for each job,
>
sure whether
this
id
is useful for further debugging. If not maybe we can ignore the job
id
from
the dashboard?
Best,
Zhijiang
--
发件人：Jin Sun
发送时间：2018年10月10日(星期三) 01:10
收件人：dev
主 题：Re: [DISCUSS] Flink Cluster Overview Dash
work you'd be doing for this
>> > change
>> > > when we migrate to React?
>> > >
>> > > Best,
>> > > Robert
>> > >
>> > >
>> > >
>> > > On Wed, Oct 10, 2018 at 8:24 AM Zhijiang(wangzhijiang999)
>
Fabian for proposing this topic.
> > > >
> > > > It is very worth improving the web dashborad for showing more useful
> > > > informations which can benefit flink users a lot.
> > > >
> > > > Just two small personal concerns:
> > >
is easy to
> > > estimate the rough duration time. Is it necessary to show the duration
> > > information to occupy the space?
> > > 2. The job name given by users can be used for identification, and the
> > > job id is automatically generated in random. I am not sure whether this
>
> 2. The job name given by users can be used for identification, and the
> > > job id is automatically generated in random. I am not sure whether this
> > id
> > > is useful for further debugging. If not maybe we can ignore the job id
> > from
> > > the dashb
in random. I am not sure whether this
> id
> > is useful for further debugging. If not maybe we can ignore the job id
> from
> > the dashboard?
> >
> > Best,
> > Zhijiang
> >
> > --
> > 发件人：Jin Sun
> > 发送时间：2018年10月10日(星期三) 01:10
> > 收件人：dev
>
random. I am not sure whether this id
> is useful for further debugging. If not maybe we can ignore the job id from
> the dashboard?
>
> Best,
> Zhijiang
>
> --
> 发件人：Jin Sun
> 发送时间：2018年10月10日(星期三) 01:10
>
dashboard?
Best,
Zhijiang
--
发件人：Jin Sun
发送时间：2018年10月10日(星期三) 01:10
收件人：dev
主 题：Re: [DISCUSS] Flink Cluster Overview Dashboard Improvement Proposal
Great job! That would very helpful for debug.
I would suggest to use small icons
Great job! That would very helpful for debug.
I would suggest to use small icons for this Job Manager/Managers when there are
too many instances (like a thousand)
May be we can also introduce locality, that task managers belongs to same rack
shows together?
Small icons can be like this:
Hi Fabian,
thanks for starting this discussion. I agree with you that Flink's web
dashboard lacks a bit of general cluster overview information on the front
page. Your mock looks really promising to me since it shows some basic
metrics and cluster information at a glance. Apart from the the source
argh, i think the screenshot is missing (at least nabble is not showing
anything). here is a link to the mockup:
https://drive.google.com/file/d/1p3wVP028_AFFLZ6fjPb41yAI8zUhgDTO/view?usp=sharing
Cheers
--
*Fabian WollertZalando SE*
E-Mail: fab...@zalando.de
Am Di., 9. Okt. 2018 um 12:46 Uh
Hi everyone,
disclaimer: i read the contribution guide about improvement requests (i.e.
i should actually just start a jira ticket) but i thought it would make
sense to run this first through the mailing list here. after collecting
some input i would then create the jira ticket.
When accessing th
16 matches
Mail list logo
