IMO we should focus on improving the developer story via DevS and look at how analyses are deployed and managed in a multi-environment scenario.
W.r.t. configuring / tuning existing analytics, I think Shankar's point is key. However, in each of these cases, we do have an analytics dashboard/app in mind right? IMO the tuning should be done from there- basically via setup flags of the gadgets themselves or a special gadget to configure stuff. Sanjiva. On Tue, Feb 23, 2016 at 4:39 PM, Selvaratnam Uthaiyashankar < [email protected]> wrote: > > > On Tue, Feb 23, 2016 at 9:34 AM, Srinath Perera <[email protected]> wrote: > >> Switching to architecture@ as this is technical discussion. >> >> Hi Sanjiva, Isabelle, >> >> We have two choices >> >> >> 1. Let user define/ configure Analytics (e.g. Alerts) via a UI. Each >> alerts is shown as a policy, and users can enable and configure it >> >> > > Who is "user" here? This is the person publishing the API, or subscribing > the API or administrator? > > If it is admin only, then +1 for configuration files. > > > > >> >> 1. Enable this only via config files ( No UI) >> >> >> WDYT? Nuwan have raised valid issues ( see below). They can be addressed, >> but would be bit complicated. >> >> I am inclined to go for config only approach. ( which fit better with No >> Carbon Console approach) >> >> We need to agree and do one thing for all analytics things. >> >> --Srinath >> >> >> ---------- Forwarded message ---------- >> From: Nuwan Dias <[email protected]> >> Date: Mon, Feb 22, 2016 at 5:44 PM >> Subject: Re: [APIM Analytics] Update on current progress >> To: Srinath Perera <[email protected]> >> Cc: Mohanadarshan Vivekanandalingam <[email protected]>, Nirmal Fernando < >> [email protected]>, "[email protected]" < >> [email protected]>, Vidura Gamini Abhaya <[email protected]>, >> Sachith Withana <[email protected]>, Fazlan Nazeem <[email protected]>, >> Tishan Dahanayakage <[email protected]>, Upul Bandara <[email protected]>, >> Maheshakya Wijewardena <[email protected]>, Janaka Ranabahu < >> [email protected]>, Tharindu Dharmarathna <[email protected]>, Sachini >> Jayasekara <[email protected]> >> >> >> Hi Srinath, >> >> Its fine to have a simple UI. It would look nice. >> >> However, please consider these when developing the UI (these are actual >> problems we've come across in support). >> >> 1. When there are a cluster of DAS nodes, to which does the UI connect >> and how are the configs replicated? >> 2. When the admin username changes on DAS, what needs to be done on APIM? >> 3. Having a UI makes it possible to change values during runtime. How do >> these affect the runtime's behaviour? >> 4. The UI should not be the only way of configuring these params, dev ops >> need to automate deployment. So think of that too. >> >> There can be more complications to address. Anyhow, if its tough to find >> solutions to any of these programatically we need to have reasonable >> answers/workarounds to address them. >> >> Thanks, >> NuwanD. >> >> On Fri, Feb 19, 2016 at 5:40 PM, Srinath Perera <[email protected]> wrote: >> >>> Nuwan, when we chatted, we said lets have a simple UI to configure. >>> >>> If we dropping the UI, we need to talk to all stakeholders and agree. >>> >>> --Srinath >>> >>> On Thu, Feb 18, 2016 at 2:40 PM, Mohanadarshan Vivekanandalingam < >>> [email protected]> wrote: >>> >>>> Hi Nuwan, >>>> >>>> I hope you can remember that we discussed the need for a UI (similar to >>>> CEP execution manager) to define thresholds/ to get parameter values for >>>> some conditions in queries. Specially for CEP queries likewise there is a >>>> requirement whether we need get parameter/threshold values for some spark >>>> queries as well.. >>>> >>>> Do you think that we don't required a UI for this ? >>>> >>>> Thanks, >>>> Mohan >>>> >>>> >>>> >>>> > > > -- > S.Uthaiyashankar > VP Engineering > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > > Phone: +94 714897591 > -- Sanjiva Weerawarana, Ph.D. Founder, CEO & Chief Architect; WSO2, Inc.; http://wso2.com/ email: [email protected]; office: (+1 650 745 4499 | +94 11 214 5345) x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
