Hi Nuwan, There are number of mail threads[3] and meeting notes about entire architecture of improved AS monitoring capabilities which includes HTTP, connector, server level monitoring with AS. The long term vision is to enable users to do any kind of monitoring through AS ( + BAM) without bringing any other product. AS team has already developed a new data capturing, publishing and dashboard components for HTTP monitoring and will be used by some other products as well, here this thread Dakishitha discussing UXD of new dashboard only. Here I recap some of the important points below ( it seems without that context this UXD discussion is bit of disconnected )
1. We have initially developed this dashboard to be hosted on BAM but during following meeting[1] we decided to move dashboards into AS like in API-M, this will be the common pattern across the platform where BAM team is no longer responsible to maintain data publishing agents and dashboards in product space. In future releases, products will ship their own dashboards and users have freedom to keep dashboards within the management node or in a dedicated dashboards node. BTW this does not mean product team duplicate and come with random dashboards, as an example HTTP monitoring feature developed by AS can be used for any HTTP monitoring use cases across the platform and ESB team already has a plan to reuse it. 2. During this[2] meeting we reviewed whole HTTP monitoring feature developed by Kalpa/Chamil and conclusion is we need to improve UX experience a lot. We suffer from this UX issues for long time specially with dashboards hence decided to focus on UX as a top priority this time. 3. We remain to use UES for these dashboards as a platform level visualization platform. At the moment above dashboard is developed on UES and Chamil is integrating UES features into AS with some helps from Manu. Having said we will not restrict by any limitations of current UES version, here the idea is we will discuss with UES team about required improvements and come to an agreement so that UES will absorb these changes down the line. Further though I'm not an expert in UES technologies I don't think we need any drastic changes form UES anyway. [1] - Invitation: AS-BAM Story - Finalize HTTP dashboards @ Wed Jun 11, 2014 3pm - 3:30pm ([email protected]) [2] - Invitation: AS HTTP Monitoring - Final Demo @ Mon Jul 7, 2014 4pm - 5pm (Kalpa Welivitigoda) [3] - AS-BAM application and server monitoring - Overall Architecture Thanks ! On Fri, Aug 1, 2014 at 5:09 PM, Nuwan Bandara <[email protected]> wrote: > Hi Dakishitha, > > UES dashboard creator does not have to support this grid, you can simply > create this as a custom site option in UES. We should build this and > package this as a default UES dashboard that will ship with UES and intern > ships with BAM (as BAM ships UES). > > Lets keep the consistency. If we are creating dashboards it has to go > through UES and not as random web applications. This also include some of > the custom pages that already there in BAM, we have to migrate them to UES > as well. > > In this way we can build dashboards for AS / MB / ESB in UES and people > can use UES as the common visualization platform. Also when you are > creating graphs / charts if they seem reusable we have to make them gadgets > and should be added to the gadget repository, so other dashboard creators > can use them. > > Regards, > /Nuwan > > > On Fri, Aug 1, 2014 at 7:09 AM, Dakshika Jayathilaka <[email protected]> > wrote: > >> @nuwan: Not really. this will use on AS with BAM support. Current UES >> doesn't support for custom level grid and tabs. so above app will not >> totally based on current UES. but i'm planning to develop the way that we >> can extend it with next UES release. >> >> *Dakshika Jayathilaka* >> Software Engineer >> WSO2, Inc. >> lean.enterprise.middleware >> 0771100911 >> >> >> On Fri, Aug 1, 2014 at 7:30 AM, Ruchira Wageesha <[email protected]> >> wrote: >> >>> Hi Dakshika, >>> >>> What I meant is, there is something wrong with the green popup, which >>> doesn't match with the rest. i.e. Several edges have rounded corners and >>> several aren't. Sometimes, if you get rid of rounded edges of the popped up >>> menu and expand it to the full width of the left vertical bar, then that >>> would be good IMO. >>> >>> /Ruchira >>> >>> >>> On Fri, Aug 1, 2014 at 12:50 PM, Dakshika Jayathilaka <[email protected] >>> > wrote: >>> >>>> @ruchira: by default it will load with collapsible left side bar. On >>>> that view sub menus will list under same main category. screen 3 implies >>>> the view on collapsed option. on that you can see the inner content by >>>> mouse hover. >>>> >>>> check below image for detail view on this.. >>>> >>>> >>>> >>>> >>>> *Dakshika Jayathilaka* >>>> Software Engineer >>>> WSO2, Inc. >>>> lean.enterprise.middleware >>>> 0771100911 >>>> >>>> >>>> On Fri, Aug 1, 2014 at 6:41 AM, Chathura Dilan <[email protected]> >>>> wrote: >>>> >>>>> Great!, Does Ruchira mean expanding that whole column and showing the >>>>> menu when clicking the icons instead of the popup menu? >>>>> >>>>> >>>>> On Fri, Aug 1, 2014 at 12:02 PM, Ruchira Wageesha <[email protected]> >>>>> wrote: >>>>> >>>>>> Really nice Daskshika. One small thing from me. i.e. I prefer if you >>>>>> can do something with the menu popped up in the third image. Personally, >>>>>> I >>>>>> feel something wrong with that, though I am not exactly clear about that >>>>>> :). >>>>>> >>>>>> >>>>>> On Thu, Jul 31, 2014 at 4:59 PM, Dakshika Jayathilaka < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I came up with UXD for HTTP monitoring dashboard user experience >>>>>>> aspects, based on[1], [2], [3]. Current target group would be DevOps, >>>>>>> Developers, CIO and can be extensible. UXDs are based on HCI major >>>>>>> principles, usability and human cognition. >>>>>>> >>>>>>> Screen Designs: >>>>>>> >>>>>>> *1. HTTP monitoring dashboard: *Mainly primary dashboard includes >>>>>>> application vice summarized data including some critical data. Color >>>>>>> blend >>>>>>> on main metro set focus to total request and error section. Inside each >>>>>>> metro block guides user eye into important data value within the block. >>>>>>> >>>>>>> *2.App dashboard: *this includes application based data as a >>>>>>> summary. when you click on each section you can reach into next extended >>>>>>> details page. >>>>>>> >>>>>>> *3. Extended Data: *this extended view may differ depending on the >>>>>>> App dashboard selection. >>>>>>> >>>>>>> *General Considerations*: Top navigation may include user specific >>>>>>> data and Application based data. Left Sidebar navigation is collapsible >>>>>>> and it would helps to create more spaces for the >>>>>>> data >>>>>>> pixels. >>>>>>> >>>>>>> Comments are welcome. >>>>>>> >>>>>>> [1] mail: [Training Project] Progress Update - AS HTTP Monitoring >>>>>>> with BAM >>>>>>> [2] mail: [Architecture] BAM Based monitoring solution for WSO2 >>>>>>> platform - Unification proposal >>>>>>> [3] mail: ASBAM application and server monitoring Monitoring >>>>>>> Parameters >>>>>>> >>>>>>> Thank you, >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> *Dakshika Jayathilaka* >>>>>>> Software Engineer >>>>>>> WSO2, Inc. >>>>>>> lean.enterprise.middleware >>>>>>> 0771100911 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Ruchira Wageesha**Associate Technical Lead* >>>>>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>>>>> <http://wso2.com>* >>>>>> >>>>>> *email: [email protected] <[email protected]>, blog: >>>>>> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >>>>>> mobile: +94 77 5493444 <%2B94%2077%205493444>* >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Chatura Dilan Perera >>>>> *(Senior Software Engineer** - WSO2 Inc.* * [Mobile])* >>>>> www.dilan.me >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Ruchira Wageesha**Associate Technical Lead* >>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> <http://wso2.com>* >>> >>> *email: [email protected] <[email protected]>, blog: >>> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >>> mobile: +94 77 5493444 <%2B94%2077%205493444>* >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > > *Thanks & Regards,* > * Nuwan Bandara | Senior Technical Lead - Solutions Architecture, WSO2 > Inc.+1 812.606.7390 <%2B1%20812.606.7390> | +1 650.745.4499 Ext 4210 > <%2B1%20650.745.4499%20Ext%204210> | http://nuwanbando.com > <http://nuwanbando.com> * <http://www.nuwanbando.com/> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
