+1. Please setup a meeting. Easier to discuss these things f2f. Azeez
On Wed, Nov 19, 2014 at 12:19 PM, Isabelle Mauny <[email protected]> wrote: > Noel, > > I don't understand the need for JMS - If a customer has a different SAM > tool, they need a plug-point - Requiring them to install/maintain a JMS > cluster does not seem right . Plus the messages would need to be > transformed to match what their tool would be - Why don't we take the same > approach as APIM manager, where publishing stats is optional and can be > sent to BAM if configured, but the monitoring handler could be changed to > publish to something else if the customer wanted to do so. > > We should also create plugins for well-know *system* management such as > Nagios (CPU, Memory, UpTime) - BAM is not a systems management tool, so the > statistics to be published there would be different. i.e. number of apps > deployed on the servers, uptime of those apps, calls per app, etc. > > Can we seat down this week and look at statistics objectives ? I am in SL > until Tues. night. > > Isabelle > > ------------------------------------------------------------------------------------- > *Isabelle Mauny* > VP, Product Management; WSO2, Inc.; http://wso2.com/ > On Wed, Nov 19, 2014 at 11:31 AM, Noel Yahan <[email protected]> wrote: > >> >> Noel Yahan >> Software Engineering Intern - WSO2 >> Mobile : +94 71-647-872-3 >> Twitter <https://twitter.com/noelyahan> | LinkedIn >> <http://lk.linkedin.com/pub/noel-yahan/48/186/a9b> | Google+ >> <https://plus.google.com/+NoelYahan> >> >> ---------- Forwarded message ---------- >> From: Noel Yahan <[email protected]> >> Date: Mon, Nov 17, 2014 at 10:23 AM >> Subject: Statistics publishing in WSO2 Operation Center >> To: WSO2 Engineering Group <[email protected]>, Sameera >> Jayasoma <[email protected]>, Sameera Perera <[email protected]>, Afkham >> Azeez <[email protected]>, Isabelle Mauny <[email protected]>, Jayanga >> Dissanayake <[email protected]> >> >> >> Current OC is able to >> >> 1. >> >> View real time statistic data of individual server nodes >> 2. >> >> Send commands to (restart , shutdown, graceful restart, graceful >> shutdown) >> >> >> Now we are working on 3, 4 and 5 >> >> >> 1. >> >> Publish data to a Message broker ActiveMQ or WSO2 MB >> 2. >> >> Analyze data from analytic tool something like WSO2 BAM >> 3. >> >> Plot analysed data on OC >> >> >> 1 and 2 is done using [OC / OCA] one way communication. OC and OCA >> transfers 4 kinds of json messages as requests and responses >> >> >> - >> >> Registration Request message [This message is to register new Server >> asset and Machine asset with some meta data] >> >> {"registrationRequest" : {"ip" : "192.168.184.1", "serverName" : "WSO2 >> Enterprise Service Bus", "serverVersion" : "4.8.1", "domain" : "Default", >> "subDomain" : "Default", "adminServiceUrl" : "https://192.168.184.1:9445/";, >> "startTime" : "1970-01-01 05:30:00", "os" : "Ubuntu 14.04.1 LTS", >> "totalMemory" : 16729.563136, "cpuCount" : 8, "cpuSpeed" : 2.7, "timestamp" >> : 1.416198017813E12, "patches" : ["patch0000", "patch0001", "patch0002", >> "patch0003", "patch0004", "patch0005"]}} >> >> >> >> - >> >> Registration Response message [This message is to make sure server >> and machine is registered or not] >> >> {"registrationResponse" : {"serverId" : "' + serverId + '"}} >> >> >> - >> >> Synchronization Request [This message is to view the real time >> statistic data] >> >> {"freeMemory" : 6882.230272, "idleCpuUsage" : 95.3554089556193, >> "systemCpuUsage" : 0.8707851215411316, "userCpuUsage" : 3.773803592421385, >> "adminServiceUrl" : "https://192.168.184.1:9445/";, "serverUpTime" : "0d >> 0h 0m 18s", "threadCount" : 80, "systemLoadAverage" : 1.42, "timestamp" : >> 1.416198022814E12} >> >> >> - >> >> Synchronization Response [This message is to capture the given >> command like restart, shutdown, graceful restart, graceful shutdown] >> >> {"synchronizationResponse" : {"status" : "updated", "serverId" : "2", >> "command" : "RESTART"}} >> >> >> Publish data to a Message broker >> >> We are publishing above messages to message broker queues or durable >> topics.Currently we are going to implement this for ActiveMQ and WSO2 MB >> >> The reason that we publishing these messages to a message brokers is some >> client may have their own analytic tool like google analytic or they may >> have a different idea to manage all those messages. So instead of >> publishing these data directly to an analytic tool like WSO2 BAM we first >> decide to publish to a message broker. >> >> Analyze data from WSO2 BAM >> >> After publishing those request, response messages to message queues or >> durable topics, to analyze those messages we need to publish those messages >> from message broker to an analytic tool like WSO2 BAM. To make it done, we >> are going to use new version of WSO2 BAM (2.5.0) and its JMS feature. It >> will allow us to communicate with any JMS enabled message brokers. >> >> Plot analysed data >> >> We are going to use published data from WSO2 BAM to process important >> information and insert those informations to a RDBMS by running a hive >> script, and reading the RDBMS data and some open source plot tool we are >> going to view graphical representation of server and machine processed >> statistics. >> >> Some of the information we are planning to extract are, >> >> eg: >> >> 1. >> >> CPU usage (last hour, day) >> 2. >> >> Memory usage (last hour, day) >> 3. >> >> Load average (last hour, day) >> >> >> >> >> >> >> >> Noel Yahan >> Software Engineering Intern - WSO2 >> Mobile : +94 71-647-872-3 >> Twitter <https://twitter.com/noelyahan> | LinkedIn >> <http://lk.linkedin.com/pub/noel-yahan/48/186/a9b> | Google+ >> <https://plus.google.com/+NoelYahan> >> >> > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **[email protected]* <[email protected]> * cell: +94 77 3320919blog: **http://blog.afkham.org* <http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez* <http://twitter.com/afkham_azeez> *linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
