Hi, On Thu, Apr 10, 2014 at 2:19 AM, Uvindra Dias Jayasinha <[email protected]>wrote:
> Is it worth doing this at the moment since APIM will be moving to ES? > Might be better to take this into consideration when implementing stats > after the migration > This change will not have any stats graph level implementations.This change is only to break the graphs in single page to multiple pages[can be done with less effort] as this has advantages of less loading time+ logically separation of stats.That's why we thought of doing this for up-coming release. Once we move with ES,with UES dashboard integration we can improve the current showing graphs usability with showing more granular level data drilled down graph views as Chanaka explained.. Thanks; > > On Thu, Apr 10, 2014 at 9:50 AM, Chanaka Jayasena <[email protected]>wrote: > >> I have seen this UI when talking with Asiri f2f. This change take away >> the dashboard concept of it out a bit. But from the logical separation of >> content and loading time vise it's a good change. One more improvement that >> I can think of is to have a landing dashboard with cumulative data got >> through less resource consuming back-end calls and have these pages as data >> drill downs. >> >> thanks, >> Chanaka >> >> >> On Wed, Apr 9, 2014 at 6:51 PM, Lalaji Sureshika <[email protected]> wrote: >> >>> Hi, >>> >>> Requirement- >>> >>> Currently all the below types of statistics shown in one page of >>> APIPublisher. >>> 1) Overall API Usage >>> 2) API Response Times >>> 3) API Last Access Times >>> 4) API Usage from Resource Path >>> 5) API Usage by user >>> 6) API Usage from Destination >>> 7) Faulty invocations >>> >>> When the published stats data size grown,this UI page is becoming >>> unresponsive to load the page. >>> >>> Solution- >>> >>> Since all above stats are in form of different statistics,we thought to >>> split each above 7 statistic types to different pages and show them >>> seperatly. >>> This way,we can show more percentage of statistics in each type and the >>> UI page loading time will be much more effective. >>> Since Asiri already working on similar improvement to Store,he'll >>> continue this task as well.. >>> >>> Appreciate your feedback on this... >>> >>> Thanks; >>> >>> -- >>> Lalaji Sureshika >>> WSO2, Inc.; http://wso2.com/ >>> email: [email protected]; >>> blog: http://lalajisureshika.blogspot.com >>> >>> >>> >> >> >> -- >> Chanaka Jayasena >> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: [email protected]; cell: +94 77 785 5565 >> blog: http://chanaka3d.blogspot.com >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Regards, > Uvindra > > Mobile: 777733962 > -- Lalaji Sureshika WSO2, Inc.; http://wso2.com/ email: [email protected]; blog: http://lalajisureshika.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
