Hi Silmy,

   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 go with option 2 we will need to share the user store with the SP
isn't it?
Is there any other usease/s where we need to share the userstore? If not I
am +1 to option 1 because that will bring all the configurations into a one
single place which is the admin app.

wdyt?

Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Wed, Aug 8, 2018 at 7:07 PM, Silmy Hasan <[email protected]> wrote:

> 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
>
> We are thinking of moving on with the second method since the first one
> creates complexity on the APIM side.
>
> *Proposed solution*
> Creating two custom widgets in SP dashboard to enable the
> admins/subscribers perform CRUD operation on those alert configuration
> tables. There will be two tables namely ApiCreatorAlertConfiguration and
> ApiSubscriberAlertConfiguration.
>
> Please provide your suggestions.
>
> Thanks,
> Silmy
>
>
> --
> 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
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to