Hi all, Please find the attached doc regarding the initial discussion on SP dashboard integration of APIM analytics.
https://docs.google.com/document/d/1zU4VpdNe9_GoSAvYDClRcfrlIYAICTH2TDTammW1ECE/edit?usp=sharing Thank you. Best Regards, Sandalu. On Fri, Oct 12, 2018 at 12:31 PM Sandalu Kalpanee <sand...@wso2.com> wrote: > Hi all, > Please find my project description and the design as below. > > The project is about revising the existing set of analytics implemented > for 2.X API Manager products to implement with 3.0 API Manager. > > *Current WSO2 APIM Analytics Model* > The current API Manager 2.6 version integrates with the Stream processor > to provide reports, statistics, and graphs on the APIs deployed in API > Manager. API Manager generates events based on its invocation pattern and > publishes them to APIM analytics. Based on the defined summarisation logic, > the data is processed. After the summarized data is generated, the APIM > Dashboard can retrieve statistics from the analyzer data-source to the UI > via the API Manager analytics client. > [image: Untitled Diagram (1).png] > > *Proposed solution* > After the summarization of API Manager data in Stream Processor, the stats > will be displayed in the Stream Processor itself through the dashboard. The > data will be retrieved from the analyzer data-source and from the siddhi > store. > Publisher, Store, and Admin stats will be separated according to the > granted permissions. > [image: Untitled Diagram (2).png] > *Issues Identified* > Currently, there are some stats which use AM_DB as its only data source. > And also, there are some stats which consume the stream data sent to APIM > analytics with further processing using AM_DB. There will be an issue > consuming data from AM_DB when generating widgets for the specific stats. > > *Ideas suggested for the issue* > > 1. The stats which use AM_DB data can reside in the APIM while other > stats being displayed in SP dashboard. > 2. The AM_DB data source can be shared with the SP in order to > generate widgets which consumes its data. > 3. A REST API can be provided for the data retrieving from APIM. > > Highly appreciated if you can provide your feedback on this. > > Thank you. > Best Regards, > -- > *Sandalu Kalpanee* > *Software Engineer - Intern* > *WSO2* > -- *Sandalu Kalpanee* *Software Engineer - Intern* *WSO2*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
