What ever gadgets we have in old Dashboard can me used in the new DS
server. But the in old app we did some costume navigation model, there is
only limited support for that in current DS. What DS currently support is
fixed one level navigation.

DAS generated gadgets can be used in DS, so DAS vs DS is a non-issue, it's
the same thing. The real question is if we want to continue the same kind
of hierarchical navigation (each node/app gets a new page in the dashboard)
we had in old AS dashboard. If so we need to continue using the old custom
app OR improve DS to support that. Improvement is not that big but but it
will be a new feature.

You are very welcome to do so if possible and we are glad to help.

On Wed, Jan 13, 2016 at 12:50 PM, Sagara Gunathunga <[email protected]> wrote:

> [Moving to architecture@ ]
>
> On Wed, Jan 13, 2016 at 12:30 PM, Lochana Ranaweera <[email protected]>
> wrote:
>
>> Hi all,
>>
>> I'm currently working on a project on adding web application statistics
>> monitoring feature to the upcoming Application Server 6.0.0. The data
>> collected from the web applications will be published to the Data Analytics
>> Server through a custom Tomcat valve, the development of which has been
>> carried out separately.
>>
>> Once the data has been published, web application statistics should be
>> displayed to the users via a Dashboard. For this, what will be the best
>> suited option out of the following?
>>
>> [1] Utilizing the gadget generation wizard of the DAS
>>
>> [2] Utilizing the Dashboard Server
>>
>>
> When we design the AS dashboard during last year we decided to support 2
> options, by default dashboard is embedded with the product (AS) and if
> required it's possible to have a dedicated dashboard node as well.
> Personally I'm not up to date about our current policy about product
> dashboards with DAS/DS, whether DS are embedded within the product or can
> we host on DAS or can we have a dedicated DS node etc.  May be DAS/DS folks
> can add more insights here ?
>
> Further given the fact that AS6 is not a Carbon based product anymore this
> is a special case as well.  I think we need a broad discussion on this,
> better to incorporate this topic with Manoj's design review on Monday, also
> let's get DAS/DS/UX folks too.
>
> Thanks !
>
>
>>
>> Any suggestions and feedback are highly appreciated.
>>
>> Thanks.
>>
>> --
>> Lochana Ranaweera
>> Intern Software Engineer
>> WSO2 Inc: http://wso2.com
>> Blog: https://lochanaranaweera.wordpress.com/
>> Mobile: +94716487055 <http://tel%2B716487055>
>>
>>
>> _______________________________________________
>> Dev mailing list
>> [email protected]
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Architect; 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
>
>


-- 
With regards,
*Manu*ranga Perera.

phone : 071 7 70 20 50
mail : [email protected]
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to