+1 for the import/export library/app. This will make the architecture clean
and easy to maintain.
Going a step further we can wrap the library and build a cli tool and maven
plugin for import and export like we envisioned in the beginning. A cli
tool will make it easier for users to create backup
On Thu, Jul 21, 2016 at 11:46 AM, Ashen Weerathunga wrote:
> Hi all,
>
> I'm writing a siddhi extension for Markov models. It can be used to detect
> abnormal user behaviors of many real world applications such as detecting
> abnormal API request patterns, detecting fraudulent bank transactions e
On Thu, Jul 21, 2016 at 11:49 AM, Nuwan Dias wrote:
> Hi Sanjeewa,
>
> What Kaveesha is suggesting in her earlier reply is to get rid of the
> import-export APIs completely. Since we now have a comprehensive
> Publisher/Store REST API, we can write a client side tool which uses these
> APIs to ex
Tested integrating a Third Party Key Manager, for both Super Tenant and
Tenant modes. Tests were carried out by calling the Jaggery APIs. No issues
were found.
[+] Go ahead and release.
On Thu, Jul 21, 2016 at 12:21 AM, Abimaran Kugathasan
wrote:
>
> *WSO2 API Manager 2.0.0-RC3 Released*
>
> Th
On Thu, Jul 21, 2016 at 12:45 PM, Sanjeewa Malalgoda
wrote:
>
>
> On Thu, Jul 21, 2016 at 11:49 AM, Nuwan Dias wrote:
>
>> Hi Sanjeewa,
>>
>> What Kaveesha is suggesting in her earlier reply is to get rid of the
>> import-export APIs completely. Since we now have a comprehensive
>> Publisher/Sto
Hi All,
I'm working on $subject.
Some of the REST APIs which we are going to introduce with IS 5.3.0
release, will need some extra protection against bot attacks.
API Requirement Prevention mechanisms
Self sign-up Human verification captcha/reCaptcha
Password recovery with email Human verificati
Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
[+] Go ahead and release.
On Thu, Jul 21, 2016 at 12:57 PM, Amila De Silva wrote:
> Tested integrating a Third Party Key Manager, for both Super Tenant and
> Tenant modes. Tests were carried out by calling the Jaggery APIs. No i
On Thu, Jul 21, 2016 at 12:32 PM, Malith Jayasinghe
wrote:
>
> On Thu, Jul 21, 2016 at 11:46 AM, Ashen Weerathunga
> wrote:
>
>> Hi all,
>>
>> I'm writing a siddhi extension for Markov models. It can be used to
>> detect abnormal user behaviors of many real world applications such as
>> detectin
Tested Throttling Levels of Resource Level, API Level, Subscription Level,
Application Level in both tenant and super tenant mode. Tested Blocking
conditions in both super tenant and tenant mode. Tested custom rules in
super tenant mode. Tested creation of throttling policies in admin
dashboard and
Hi All,
I have planned to develop UniqueTimeBatchWindow, UniqueLengthBatchWindow
Extension for Siddhi. We already have TimeWindow, TimeBatchWindow and
UniqueTimeWindow. Same to length
also.
Currently, I'm planning to implement UniqueBatchWindow which is support for
both time and length.
Please a
We really don't need to have both in the same implementation. But we can
have both in common repo called UniqueBatchWindow.
Regards
Suho
On Thu, Jul 21, 2016 at 2:44 PM, Rajjaz Mohammed wrote:
> Hi All,
>
> I have planned to develop UniqueTimeBatchWindow, UniqueLengthBatchWindow
> Extension for
Hi Malith,
You don't need to define the matrix. You need to have an input stream which
consists of user id and state. So based on the input data it will create
the transition matrix itself and give notifications according to that. But
It will need a considerable amount of data to build a matrix
wi
Hi Suho,
We really don't need to have both in the same implementation. But we can
> have both in common repo called UniqueBatchWindow.
>
> Both are not in same implementations.
>
> I have planned to develop UniqueTimeBatchWindow, UniqueLengthBatchWindow
>> Extension for Siddhi. We already have Ti
Hi Ashen,
On Thu, Jul 21, 2016 at 2:59 PM, Ashen Weerathunga wrote:
> Hi Malith,
>
> You don't need to define the matrix. You need to have an input stream
> which consists of user id and state. So based on the input data it will
> create the transition matrix itself and give notifications accord
Hi Ashen,
Thanks for the explanation.
Note that there are case where the state transition matrix is already known
(and fixed). People derive these metrics by analyzing very large data sets
which come from long running experiments. In such cases we want the user to
provide this transition matrix as
Sorry, I miss read the mail. +1
Regards
Suho
On Thu, Jul 21, 2016 at 3:02 PM, Rajjaz Mohammed wrote:
> Hi Suho,
>
> We really don't need to have both in the same implementation. But we can
>> have both in common repo called UniqueBatchWindow.
>>
>> Both are not in same implementations.
>
>>
>>
On Thu, Jul 21, 2016 at 3:22 PM, Malith Jayasinghe wrote:
> Hi Ashen,
> Thanks for the explanation.
>
> Note that there are case where the state transition matrix is already
> known (and fixed). People derive these metrics by analyzing very large data
> sets which come from long running experimen
Hi Lasantha,
Yes. we can keep the count of no of transitions happened between each and
every state and update the probabilities according to that. We know that
all transition probabilities from a particular state to other states should
be equal to 1. So based on that we can update the probabilities
Hi All,
We are closing this vote. Vote hasn't got any -1 votes. We will proceed
with publishing the maven artifacts to nexus and hosting the GA pack.
Regards,
Dinusha.
On Thu, Jul 21, 2016 at 3:53 AM, Dinusha Senanayaka
wrote:
> Tested with following scenarios and found no issue.
>
> - Throttl
Hi Chamara,
Publishing events[1] and Device Monitoring [2] are not related each other.
Since Android agent is capable of sending out critical events to WSO2 DAS
server, There are some configurations to enable in EMM server to publish
events in DAS Server. Here [1] Managing Event publishing
provide
Hi all,
This is to discuss $subject.
Most of the issues we faced were due to the unavailability of a default
overlay network/ SDN in mesos. Because of that, its not possible to
communicate from container to container directly. The network related
issues are discussed in detail in the mail [1] in
Hi Chamara,
When it comes to EMM Monitoring Dashboard, we are not retrieving data from
DAS.
Instead, we use the data from our product databases themselves as our
current monitoring use-cases only carry the use of snapshot data and not
historical data.
Regards,
Dilan.
*Dilan U. Ariyaratne*
Senior
When managing devices, administrator must be notified of events occurring
on the user's devices that reduce the effectiveness and efficiency of the
tasks performed by a device, so that He can take immediate action and
correct it.
For example, if a cooperate application is utilizing a high CPU or me
On Thu, Jul 21, 2016 at 6:05 PM, Hasunie Adikari wrote:
> Hi Chamara,
>
> Publishing events[1] and Device Monitoring [2] are not related each other.
> Since Android agent is capable of sending out critical events to WSO2 DAS
> server,
>
What is the usage of this in a real world scenario?
> T
>
> One downside I see in the client-side tool approach is that it will result
> in a few http calls between the client and server instead of just 1 http
> call (as before). But still I think its fine since this is not an end-user
> type of app but rather something that will be used at a much small
On Thu, Jul 21, 2016 at 6:18 PM, Isuru Haththotuwa wrote:
>
> After patching to get over the connection issue [2], another issue is seen
> where after the connection is established between spark client and
> mesos(spark) master, where the spark client just hang executing after the
> log lines [3]
Hi,
We need to drop RC3 due to [1]. We'll call for an RC4 soon.
[1] - https://wso2.org/jira/browse/APIMANAGER-5292
Thanks,
NuwanD.
On Thu, Jul 21, 2016 at 2:42 PM, Harsha Kumara wrote:
> Tested Throttling Levels of Resource Level, API Level, Subscription Level,
> Application Level in both ten
Hi all,
How does the EMM DAS Integration [1] and Device Monitoring [2] relate to
each other?
Are we using the Stream definitions defined in DAS in [2] in the EMM
dashboard in [1]. If so I cannot see the exact mapping of what goes into
DAS and what is available in EMM Dashboard side.
[1]
https://
*WSO2 API Manager 2.0.0-RC4 Released*
This is the 4th Release Candidate of the WSO2 API Manager 2.0.0
Source & binary distribution files of API Manager 2.0.0-RC4 :
Runtime :
https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc4
Analytics :
https://github.com/wso2/analyti
is that testing includes, full scaled HA deployment ?
On Thu, Jul 21, 2016 at 2:12 AM, Harsha Kumara wrote:
> Tested Throttling Levels of Resource Level, API Level, Subscription Level,
> Application Level in both tenant and super tenant mode. Tested Blocking
> conditions in both super tenant and
WSO2 App Manager-1.2.0 Released !
WSO2 App Manager team is pleased to announce the *1.2.0* release of WSO2
App Manager.
WSO2 App Manager is a complete solution for publishing, consuming and
managing all aspects of an application and its lifecycle. Organizations
with the need to provide centraliz
+ for doing advanced analysis/prediction based on the data is received from
sensors. Each of these scenarios will require different types of analysis
and prediction algorithms. It might be a good idea to figure out which ones
are important and then work in that order.
Note that it is important to
Yes, testing includes HA deployment.
On Fri, Jul 22, 2016 at 2:53 AM, Vanjikumaran Sivajothy
wrote:
> is that testing includes, full scaled HA deployment ?
>
> On Thu, Jul 21, 2016 at 2:12 AM, Harsha Kumara wrote:
>
>> Tested Throttling Levels of Resource Level, API Level, Subscription
>> Level
Hi Abimaran
Is the analytics pack[1] an RC3 or an RC4
[1] https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
regards,
Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300
Hi Shavantha,
Analytics pack hasn't required any changes from RC3. So, it's the same as
RC3.
On Fri, Jul 22, 2016 at 10:43 AM, Shavantha Weerasinghe
wrote:
> Hi Abimaran
>
> Is the analytics pack[1] an RC3 or an RC4
>
> [1] https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc3
>
>
>
>
Tested
- API import-export
- Store Self Sign-up
- Store search
- Tested main functionalities with MySQL, PostgreSQL and on Windows
No issues found.
[+] - Stable - go ahead and release
Thanks.
On Fri, Jul 22, 2016 at 1:25 AM, Abimaran Kugathasan
wrote:
> *WSO2 API Manager 2.0.0-R
Hi All,
I'm planing to improve APIM import/export tool to support bulk import and
bulk export of APIs.
When considering the bulk export, there it came up to a discussion point on
how to get the API list to be export. Considering several facts, came up
with two suggestions as follows.
[1]. Asking
Tested analytics and smoke tested APIM on db2, mssql, mysql, mysql5.7,
oracle, postgre and h2.
No issues found.
[+] - Stable - go ahead and release
Thanks.
On Fri, Jul 22, 2016 at 10:48 AM, Thilini Cooray wrote:
> Tested
>
>- API import-export
>- Store Self Sign-up
>- Store search
Hi,
Please find the meeting notes in [1]. I have following considerations
regarding the improvements we have discussed.
(1) Even though we have configured to load the email template from
EventPublisher(analytics side), the placeholder values has to be sent as
meta data/correlation data/payload d
Thanks for the great use cases, we'll consider them too, as the first
attempt we are trying to show what we collect in a meaningful way, then one
by one we'll be adding predictions and grouped analytics on top of this.
Regards
Suho
On Fri, Jul 22, 2016 at 10:09 AM, Malith Jayasinghe
wrote:
> +
Tested
- basic API flow
- SSO with IS 5.2.0 beta2
- Reverse Proxy with SSO with IS 5.2.0 beta2
and no issues found.
[x] - Stable - Go ahead and release.
On Fri, Jul 22, 2016 at 11:28 AM, Rukshan Premathunga
wrote:
> Tested analytics and smoke tested APIM on db2, mssql, mysql, m
Tested below with DB2 and SQL server 2008.
* Basic APIM functionality.
* Alert subscriptions.
* Log analyzer in a multi-tenant environment.
No issues found
[+] Stable - go ahead and release.
On Fri, Jul 22, 2016 at 11:28 AM, Rukshan Premathunga
wrote:
> Tested analytics and smoke tested API
+1 for doing a real use case scenario that exhibits the full potential of
the analytics framework provided for the IoT Platform.
As a start its best we focus on the most straight-forward analytics (eg:
individual data flow over hourly periods of time, average of data over a
period like a day/week/
43 matches
Mail list logo
