Hi Pasidu,
Q1) We are planning to apply policies like restricting the removal of agent
from the laptop. However these capabilities will be saved for another phase
after the core functionalities are done. I will update this thread once we
start those implementations.
Q2) a) We can save data in the client side until the connection established
again. However exact implementation will change with the data purging plain
in DAS.
b) This will depend on the use case. If infra team installing OS
behalf of the users they can install agent in all operating systems. If
users are allowed the change / add operating systems they have to install
agent by them-self. We will have a unified agent for all 3 operating
systems.
Yeah, that's possible. For this device type also we can reuse some units
from Android Sense dashboard.
Thank you very much for for pointing out these information.
On Wed, Jul 5, 2017 at 10:57 PM, Pasindu Jayaweera <[email protected]>
wrote:
> Hi Lahiru,
> Q.) Other than pushing data from the laptop, will there be any operations
> or policies than can be applied from the server-side?
>
> Q) What could be the agent's behavior;
>
> a.) when the laptop is out of the network?
>
> b.) when the laptop has multiple operating systems?
>
>
> When designing analytics views and creating ML plans, I would like to
> suggest to make them in such a way that those units can be plugged not only
> with the laptops, but also with any device type that provide the same stats
> that you are planning to get from the laptops at this moment. Because the
> stats like RAM, CPU utilization can be fetched from most of the other
> devices as well. So that upon the use case, those device types can reuse
> the same unit in future. WDYT?
>
> Thanks.
>
> On Wed, Jul 5, 2017 at 8:19 PM, Lahiru Madushanka <[email protected]>
> wrote:
>
>>
>> Hi all,
>>
>> Currently I am working on a new device type for IOTS which can collect
>> stats from Laptops and use them for analytics and decision making process.
>> This is achieved by an agent running on PC which pushes collected stats to
>> the IOTS in given time intervals.
>>
>> Sample use case 1 :- Average ram / CPU utilization of team X can be use
>> as a measurement when buying new PCs for team X.
>>
>> Sample use case 2 :- Prediction of average memory requirement of team X
>> for next year
>>
>> Development Phases
>>
>> Phase 1
>> Developing the initial agent which runs on PC and publish statistics to
>> the IoTS through the MB.
>> Creating event receivers / publishers and execution plans in DAS to
>> handle data.
>> Creating initial analytics and real time analytics views for a single
>> device
>>
>> Phase 1 was already done by Thisari Patabendi.
>>
>> Phase 2
>> Adding "Device profiles" to the device database.
>> Data purging and summarization
>> Implementing group analytics view for roles "team lead" and "infra level
>> user".
>>
>> Phase 3
>> Collect data by running agent on several test machines.
>> Applying analytics on collected data and create ML plan.
>> Creating analytic result dashboards
>>
>> Suggestions are highly appreciated.
>>
>> Thanks.
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> *Pasindu Jayaweera*
> Software Engineer | WSO2 Inc
> Mobile: +94 718187375 <+94%2071%20818%207375>
> Blog: blog.pasindujayaweera.com
> <http://wso2.com/signature>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
