Open Stack

I am thinking a application level monitoring framework may fit your request 

-----原始邮件-----
发件人: "mcheung63" <mcheung63 at hotmail.com>
发送时间: ‎2013/‎7/‎21 15:51
收件人: "laserjetyang" <laserjetyang at gmail.com>
抄送: "openstack at lists.launchpad.net" <openstack at lists.launchpad.net>
主题: 回覆： [Openstack] VM monitoring design brainstorm

yes, thats why i want to enhance it


-------- 原有訊息 --------
由： laserjetyang <laserjetyang at gmail.com> 
日期： 2013-07-21 15:24 (GMT+08:00) 
至： Peter Cheung <mcheung63 at hotmail.com> 
抄送： openstack at lists.launchpad.net 
主題： Re: [Openstack] VM monitoring design brainstorm 



you were actually asking a application level monitoring, and I am afraid OpenStack is not very good at monitoring at this level. I usually monitor those common applications (mysql, tomcat) through some other third party monitoring tools.




On Sun, Jul 21, 2013 at 1:33 PM, Peter Cheung <mcheung63 at hotmail.com> wrote:

Hi All 
   https://www.dropbox.com/s/vuipa1a2ilw7z9p/titan-instance-design-20130621.png  I am designing the VM monitor screen. I have asked many people, some of them used VMware for few years but their requirements are simple, most of the people told me they just need to know the CPU+RAM+network information. But I think i can do a little bit more. For example, I think it is good to record these information
1) CPU+RAM+network for each app running inside the VM. So people can see why the VM so busy.
2) If you are running a web server inside the VM, it would be nice to know how many concurrent connection to your server, right?
3) If you are running MySQL cluster, it is nice to tell you which query is eating the memory


Any other good idea?

Thanks 
from Peter

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack at lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130723/e71b1ba6/attachment.html>