I was able to find the UI. Have we documented this? On Mon, Sep 24, 2018 at 11:00 AM Fazlan Nazeem <[email protected]> wrote:
> Hi Praminda, > > Did we add this UI to the APIM 2.6.0 RC3 release? I am unable to find this > in publisher/Store portals. > > On Tue, Sep 4, 2018 at 5:10 PM Praminda Jayawardana <[email protected]> > wrote: > >> Yes. Dropdown is searchable. Listed APIs/Apps will be filtered by the >> subscriber. >> >> >> On Tue, Sep 4, 2018 at 5:06 PM Fazlan Nazeem <[email protected]> wrote: >> >>> +1. >>> >>> Does the drop down have a search functionality in it? Because listing >>> all APIs or Applications in a dropdown may not be scalable. >>> >>> On Tue, Sep 4, 2018 at 9:59 AM Praminda Jayawardana <[email protected]> >>> wrote: >>> >>>> Hi All, >>>> >>>> We decided to move this from SP to APIM to solve several complications. >>>> >>>> 1. Hard to provide API/Application list in SP side. User need to >>>> manually type API and Application names >>>> 2. Multi tenancy is not supported in SP. >>>> >>>> Current mock UI looks like following in the API Store. >>>> >>>> [image: image.png] >>>> >>>> Thanks, >>>> Praminda >>>> >>>> On Thu, Aug 9, 2018 at 11:07 AM Silmy Hasan <[email protected]> wrote: >>>> >>>>> Hi Ishara, >>>>> >>>>> The idea was not to share the user store with SP , Within SP we will >>>>> not check whether the user is a subscriber or API Creator, we will let the >>>>> user make changes to those tables if the user is an Admin. The admin can >>>>> be >>>>> a subscriber or Api Creator. >>>>> >>>>> Ideally we should have this in publisher portal and store from APIM >>>>> and publish it from APIM as mentioned in the option 1, but we are thinking >>>>> of going for the second one because of the request from the APIM team as >>>>> it >>>>> creates lot of complexity on their side in publishing this as a stream. >>>>> >>>>> On Thu, Aug 9, 2018 at 10:31 AM, Silmy Hasan <[email protected]> wrote: >>>>> >>>>>> Hi Dinusha, >>>>>> >>>>>> According to what is discussed with the APIM team( Fazlan and >>>>>> chamila) we will let the admins configure values for both tables, and >>>>>> within the SP we will not check whether he is an Api Creator or >>>>>> Subscriber. >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Aug 9, 2018 at 10:16 AM, Dinusha Dissanayake < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Silmy, >>>>>>> >>>>>>> Hi all, >>>>>>>> >>>>>>>> According to the current implementation of APIM Analytics , we use >>>>>>>> percentile values to find out certain threshold values (eg:- Abnormal >>>>>>>> request count) . Since generating alerts using percentile values >>>>>>>> creates >>>>>>>> lots of complexity to the users of the alert, it was decided to move >>>>>>>> towards a user configurable system where admins and subscribers can set >>>>>>>> those threshold values directly. >>>>>>>> >>>>>>>> *Note* >>>>>>>> >>>>>>>> - There will not be any default values for those thresholds. >>>>>>>> - The alerts will not be generated to the particualr API or >>>>>>>> application untill the admins or subscribers set a value for those >>>>>>>> thresholds. >>>>>>>> >>>>>>>> Two possible ways could be identified to let the admins and >>>>>>>> subscribers to configure these values, >>>>>>>> >>>>>>>> 1. Let the admins or subcribers set those values in APIM side >>>>>>>> and publish it to SP as a stream. A siddhi app can be written to >>>>>>>> listen to >>>>>>>> the stream an store it in database >>>>>>>> 2. Let the admins or subscriber set a value at SP dashboard >>>>>>>> itself using a dashboard widget >>>>>>>> >>>>>>>> If we are letting subscribers to set the throshold values, the >>>>>>> subscriber has to login to SP ? If so, it would reduce the user >>>>>>> experience >>>>>>> IMO. Can you please explain how the flow goes for subscribers when >>>>>>> setting >>>>>>> these values? >>>>>>> >>>>>>> -- >>>>>>> Dinusha Dissanayake >>>>>>> Software Engineer >>>>>>> WSO2 Inc >>>>>>> Mobile: +94712939439 >>>>>>> <https://wso2.com/signature> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Shilmy Hasan >>>>>> Associate Software Engineer | WSO2 >>>>>> >>>>>> E-mail :[email protected] >>>>>> Phone :0779188653 >>>>>> web : http://www.wso2.com >>>>>> >>>>>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Shilmy Hasan >>>>> Associate Software Engineer | WSO2 >>>>> >>>>> E-mail :[email protected] >>>>> Phone :0779188653 >>>>> web : http://www.wso2.com >>>>> >>>>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>> >>>> >>>> -- >>>> >>>> *Praminda Jayawardana* >>>> Senior Software Engineer >>>> WSO2 Inc.; http://wso2.com >>>> Mobile : +94 (0) 716 590918 >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> >>> >>> -- >>> Thanks & Regards, >>> >>> *Fazlan Nazeem* >>> Senior Software Engineer >>> WSO2 Inc >>> Mobile : +94772338839 >>> [email protected] >>> >> >> >> -- >> >> *Praminda Jayawardana* >> Senior Software Engineer >> WSO2 Inc.; http://wso2.com >> Mobile : +94 (0) 716 590918 >> > > > -- > Thanks & Regards, > > *Fazlan Nazeem* > Senior Software Engineer > WSO2 Inc > Mobile : +94772338839 > [email protected] > -- Thanks & Regards, *Fazlan Nazeem* Senior Software Engineer WSO2 Inc Mobile : +94772338839 [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
