Hi All,

Try to stick to the existing libraries within platform as much as
possible(d3,vega,viz etc..). These are proven to provide all necessary
functionalities to render gadget UIs.

Regards,
UdaraR

On Wed, Mar 2, 2016 at 7:15 AM, Lochana Ranaweera <locha...@wso2.com> wrote:

> Hi Tharik,
>
> Ideally, the gadgets should directly call the DAS Analytics REST API to
> get the summarized information. At the moment, the gadgets are working with
> our own API to retrieve data out of a mysql database. However, the final
> outcome of this project will have the gadgets calling our own API which in
> turn calls the DAS REST API.
>
> As of now, flot is being used as the javascript plotting library. Also I
> will look in to incorporating VizGrammer when creating chart gadgets. :)
>
> Thanks.
>
> On Tue, Mar 1, 2016 at 8:56 AM, Tharik Kanaka <tha...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> If new charts are going to be implemented for these gadgets, it is better
>> to use VizGrammar [1] as it has been using as generic charts for
>> implementing analytics for products such as ESB.
>>
>> [1] http://wso2.github.io/VizGrammar/samples/
>>
>> Regards,
>>
>> On Mon, Feb 29, 2016 at 7:54 PM, KasunG Gajasinghe <kas...@wso2.com>
>> wrote:
>>
>>>
>>> It seems these gadgets should directly call the DAS analytics API to get
>>> the summarized info.
>>>
>>> For the folder structure, may be we can create a top-level module called
>>> webapp-analytics and create the CApp there. If there are other artifacts
>>> other than the CApp, then we'll have to add the capp as a sub-module.
>>>
>>> On Fri, Feb 26, 2016 at 4:45 PM, Tharik Kanaka <tha...@wso2.com> wrote:
>>>
>>>> Hi Lochana,
>>>>
>>>> Are you going to use existing analytics API used in DAS? Apart from
>>>> that what are the javascript chart libraries are you going to use for these
>>>> gadgets?
>>>>
>>>> Regards,
>>>>
>>>> On Fri, Feb 26, 2016 at 3:46 PM, Lochana Ranaweera <locha...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Hi KasunG,
>>>>>
>>>>> The final deliverable of the dashboard will be a set of gadgets that
>>>>> can be deployed in the DS separately. It was suggested that ideally with
>>>>> the AS build the gadgets could be packed as a car file.
>>>>>
>>>>> As of now, the gadgets are working along with an API that provides the
>>>>> gadgets with properly structured data obtained out of a mysql database. 
>>>>> The
>>>>> table structure for the tables in the mysql database is to be provided
>>>>> using a spark script.
>>>>>
>>>>> The following will have to be done by a user in order view web
>>>>> application statistics by means of a dashboard created using these gadgets
>>>>>
>>>>> - Publish webapp statistics to the DAS using publisher valve at AS
>>>>> - Execute the given Spark script to summarize the event data in to a
>>>>> database
>>>>> - Configure the datasource definition in Dashboard Server to retrieve
>>>>> data from the database
>>>>> - Create and publish a dashboard using preferred HTTP monitoring
>>>>> gadgets through dashboard server portal
>>>>>
>>>>> Thanks.
>>>>>
>>>>> On Fri, Feb 26, 2016 at 2:08 PM, KasunG Gajasinghe <kas...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> +architecture
>>>>>>
>>>>>> Hi Lochana,
>>>>>>
>>>>>> Can you describe what is the final deliverable of the dashboard?
>>>>>> Also, please explain briefly how the users are going to use these gadgets
>>>>>> as well as all other dependencies these need. Based on that, we can 
>>>>>> figure
>>>>>> out how the folder structure should be.
>>>>>>
>>>>>> Btw, can you explain the overall effort required to port these
>>>>>> gadgets? What needs to be done?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> On Fri, Feb 26, 2016 at 12:42 PM, Lochana Ranaweera <
>>>>>> locha...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> This is regarding the HTTP Monitoring Dashboard for AS 6.0.0. It is
>>>>>>> to be deployed as a collection of user preferred set of gadgets in the
>>>>>>> Dashboard Server.
>>>>>>> As of now, I have ported the* basic* HTTP monitoring functionality
>>>>>>> as separate gadgets for DS.
>>>>>>>
>>>>>>> A typical HTTP monitoring gadget has the following structure:
>>>>>>>
>>>>>>> gadget-name
>>>>>>>    ├── css
>>>>>>>    ├── js
>>>>>>>    ├── fonts
>>>>>>>    ├── images
>>>>>>>    ├── index.xml
>>>>>>>    └── gadget.json
>>>>>>>
>>>>>>> What will be the best structure to version control thus created
>>>>>>> gadgets in the given branch
>>>>>>> <https://github.com/wso2/product-as/tree/wso2as-6.0.0> of AS 6.0.0?
>>>>>>> Should it be in modules or should it be inside contents directory in
>>>>>>> the distribution module?
>>>>>>> The directory structure of the build for new AS 6.0.0 is given
>>>>>>> below:
>>>>>>>
>>>>>>>
>>>>>>> ​
>>>>>>> Appreciate your suggestions on this matter.
>>>>>>>
>>>>>>> Thanks and Regards,
>>>>>>> --
>>>>>>> Lochana Ranaweera
>>>>>>> Intern Software Engineer
>>>>>>> WSO2 Inc: http://wso2.com
>>>>>>> Blog: https://lochanaranaweera.wordpress.com/
>>>>>>> Mobile: +94716487055 <http://tel%2B716487055>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>>>>>> email: kasung AT spamfree wso2.com
>>>>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>>>>> blog: http://kasunbg.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lochana Ranaweera
>>>>> Intern Software Engineer
>>>>> WSO2 Inc: http://wso2.com
>>>>> Blog: https://lochanaranaweera.wordpress.com/
>>>>> Mobile: +94716487055 <http://tel%2B716487055>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Architecture mailing list
>>>>> Architecture@wso2.org
>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Tharik Kanaka*
>>>>
>>>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>>>>
>>>> Email: tha...@wso2.com | Web: www.wso2.com
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>>> email: kasung AT spamfree wso2.com
>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>> blog: http://kasunbg.org
>>>
>>>
>>>
>>
>>
>>
>> --
>>
>> *Tharik Kanaka*
>>
>> WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka
>>
>> Email: tha...@wso2.com | Web: www.wso2.com
>>
>
>
>
> --
> Lochana Ranaweera
> Intern Software Engineer
> WSO2 Inc: http://wso2.com
> Blog: https://lochanaranaweera.wordpress.com/
> Mobile: +94716487055 <http://tel%2B716487055>
>
>
> _______________________________________________
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,
UdaraR
_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to