agreed, I think challenge it making it clear that power of a full blown analytics platform is behind the IoT product. I think from the doc, and site, it is not apparent.
Also, in future version, IoT tooling can carry Analytics tooling intergated . --Srinath On Tue, May 17, 2016 at 3:47 PM, Sumedha Rubasinghe <[email protected]> wrote: > Srinath, > We are already doing this. > > For device type analytics, you can include those queries as part of device > plugin. We deploy them as CAR files into DAS. > For example > https://docs.wso2.com/display/IoTS100/Device+Manufacturer#DeviceManufacturer-WritingbatchanalyticsforConnectedCup > > For anything beyond (full blown scenarios where device type view is too > low level), you can directly write it. > > On Tue, May 17, 2016 at 12:50 PM, Srinath Perera <[email protected]> wrote: > >> Thanks Sumedha. >> >> Suho, are we going to support users to write queries CEP, Spark on top of >> this data IoTS captured? ( or is it for future releases?) IMO that will add >> lot of values to the story. >> >> --Srinath >> >> On Tue, May 17, 2016 at 10:59 AM, Sumedha Rubasinghe <[email protected]> >> wrote: >> >>> >>> >>> On Tue, May 17, 2016 at 10:45 AM, Srinath Perera <[email protected]> >>> wrote: >>> >>>> >>>> 1. When you land on the doc, it is not clear where you should go >>>> >>>> Planning to fix this Srinath. >>> >>>> >>>> 1. There is a quick start guide and "Getting started with IoTS" >>>> server >>>> 2. in #2 "Start the Virtual Fire-Alarm", it does not tell you have >>>> to go to device section to find "virtual fire alarm" >>>> 3. When I said srinathFirealarm, it does not like the name but did >>>> not tell me why >>>> >>>> I used the same name (srinathFirealarm) and it worked. Did you try on a >>> latest nightly build? >>> >>>> >>>> 1. Download instructions and "Example: Navigate to the device agent >>>> file that is in the <IOTS_HOME>/device_agents/virtual_firealarm >>>> directory." >>>> does not match >>>> >>>> This is just giving an example directory to which you may have >>> extracted the device agent. >>> >>> >>>> 1. When I click on buzzer, why should I pick a protocol and state? >>>> Cannot we pick protocol automatically ( based on how device connected) >>>> and >>>> state via a drop down box? >>>> >>>> >>> We will fix this to be a drop down with default selected. This is >>> because we have included both MQTT and XMPP support in this example. >>> >>> >>>> >>>> 1. [image: Inline image 1] >>>> 2. Add end of "Device onwer" tutorial, can we point to how to write >>>> a new device. Also can we have a mobile app that will make your phone a >>>> device? >>>> >>>> Android Sense is this one. >>> It's basically using mobile phone as a gateway with bunch of sensors >>> connected. >>> >>> >>> >>> >>>> BTW, demo is nice!! >>>> >>>> --Srinath >>>> >>>> -- >>>> ============================ >>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >>>> Site: http://home.apache.org/~hemapani/ >>>> Photos: http://www.flickr.com/photos/hemapani/ >>>> Phone: 0772360902 >>>> >>> >>> >>> >>> -- >>> /sumedha >>> m: +94 773017743 >>> b : bit.ly/sumedha >>> >> >> >> >> -- >> ============================ >> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera >> Site: http://home.apache.org/~hemapani/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> > > > > -- > /sumedha > m: +94 773017743 > b : bit.ly/sumedha > -- ============================ Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://home.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
