Hi all,

With API manager C5 development, are planning to come up with a new web app
for analytics which will include all stats graphs, which were previously in
publisher and store. With this effort, all stats graphs will be moved from
publisher and store to the analytics app. Depending on the role of the user
who logs into this app, we will filter which gadgets will be shown.

The statistic data writing model will still be the same, where DAS will
write summarized data to the stats DB which will be then read by the charts
in the analytics app of API manager through a REST api. Note that this is
not the DAS REST api, but an MSF4j microservice which will reside on API
Manager.

We have about 17 charts in API Manager 2.1.0. These charts can be
categorized into three categories: Api, Application and Subscription. We
will anyway have to review and finalize whether we are going to replicate
the same set of graphs in C5 as well. This discussion is about the REST API
for the analytics app.

Currently, I have the following design in mind.


*REQUEST FORMAT*


GET
https://localhost:9292/api/am/analytics/v1.0/charts/charts/category/chartName

Each chart will have its own resource with specific query params for
filtering.



*example*


https://localhost:9292/api/am/analytics/v1.0/charts/api/api_usage

https://localhost:9292/api/am/analytics/v1.0/charts/application/applications_created_over_time

https://localhost:9292/api/am/analytics/v1.0/charts/subscription/api_subscriptions





*RESPONSE FORMAT*


Each chart's response will be mapped into separate DTOs. For this, we could
have a parent-child relationship modeled in swagger so that we do not
duplicate fields.


Any feedback?


-- 
Thanks & Regards,

Fazlan Nazeem

*Senior Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
[email protected]
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to