admin's Posts

Hi Kevin, Thank you for your interest in Hyperic HQ. The scalability of HQ depends on numerous factors. - Number of hardware platforms being monitored - Number of resources on each plat... See more...
Hi Kevin, Thank you for your interest in Hyperic HQ. The scalability of HQ depends on numerous factors. - Number of hardware platforms being monitored - Number of resources on each platform being monitored - Number and collection intervals of metrics - Number of alert definitions - Database performance and throughput Each of these factors, of course, can be determined by the user. Our internal database is actually PostgreSQL, which is not a limiting factor. We have customers running large deployments for datacenters of hundreds of platforms on both PostgreSQL and Oracle. I am sure that HQ can scale to fit your environment. However, we would need to determine your specific monitoring and management requirements and see if any tradeoffs need to be made to gain the coverage that you need. I will say that for those customers with larger deployments, the database is typically running on a separate dedicated server and that the HQ server has typically around 16GB of memory. We also have the ability to create a high-availability environment for our enterprise customers by creating a farm of data processing nodes that partition your server farm to report to different data processors. This can significantly improve HQ's capacity. This will, of course, involve a few more steps in the installation and configuration of HQ. I hope this helps to answer your question. Feel free to ping me with any further questions. Thanks! Charles On Jun 9, 2006, at 12:48 PM, Kevin Foster wrote: > Howdy, > > I am a sys admin in a development environment of 900+ servers. We > currently use Nagios to monitor our systems in use which is about > 830. I was wondering what the scalability of HQ is? > > Our current HQ server: > Dell 1750, Dual 3Ghz, 4GB mem > OS: Red Hat 4.0 > The HQ install is running on the internal database server but if we > decide to go with HQ we will move it to Oracle. > > Any information on this would be appreciated. > > Also, good job on the product! We like what we have seen so far. > > Thank you, > > Kevin Foster
Can you post the VM and the full log so we can take a look? Thanks.
Hi, Which build of VC is installed in the 2k3 sp1 VM? Is it VC Server or Client or both? Thanks.
VMImporter2 build 24380 is not compatible with the RC2 ESX/VC builds. We will be releasing a Beta 3 of VMImporter 2 very shortly which will be able to connect to the ESX/VC RC2. Thanks.
At this time, VMImporter 2 does not support importing LSR images of machines which contain dynamic disks.
Hi, Can you post the VM so we can take a look? Thanks.
Can you post the VM that you restored the image to along with the log file so we can take a look at it? Thanks.
Unfortunately only Resin 3.x is currently supported in the new plugin. I did some looking into 2.x, but there are not many metrics there. We could collect a host of JVM metrics similar to: ... See more...
Unfortunately only Resin 3.x is currently supported in the new plugin. I did some looking into 2.x, but there are not many metrics there. We could collect a host of JVM metrics similar to: http://support.hyperic.com/confluence/display/DOCSHQ27/Sun+JVM But nothing Resin specific without some sort of instrumentation. The Resin 3.x metrics, control, and inventory properties are up on our 2.7 docs: http://support.hyperic.com/confluence/display/DOCSHQ27/Caucho+Resin On Jun 7, 2006, at 6:18 PM, Dan Gorman wrote: > That's awesome to hear! Would this be applicable to both Resin 2.x > and 3.x ?
Hi Sven, The Vm Importer doesn't know how to create ESX vmdk format unless it connects directly to an ESX server. As you discovered, the current VM Importer beta is not compatible with the ESX... See more...
Hi Sven, The Vm Importer doesn't know how to create ESX vmdk format unless it connects directly to an ESX server. As you discovered, the current VM Importer beta is not compatible with the ESX 3 RC2 release, but we are working on getting a RC2 compatible release out the door Real Soon Now! Thanks, Bryan
Your question will be better served in one of the ESX 3/ VC 2 beta forums: http://www.vmware.com/community/category.jspa?categoryID=78
The charts that you are referring to are the Indicator Charts. The indicator charts are displayed as column charts, where the area of each column indicates the value range (the high and low value... See more...
The charts that you are referring to are the Indicator Charts. The indicator charts are displayed as column charts, where the area of each column indicates the value range (the high and low values) of the metric. The average value of the metric is indicated by the cross in the column. Each column represents 1/60 of the time range that you have selected for the metric display range. If there were only 1 data point in that time range, or that the data points collected in that time range all have the same value, then you would see just the blue dot, rather than a range of values.
I've logged a bug to better detect the case where /tmp is not writable: http://jira.hyperic.com/browse/HHQ-67 The no-xlibs problem seems to pop up quite frequently. We have an existing bug ... See more...
I've logged a bug to better detect the case where /tmp is not writable: http://jira.hyperic.com/browse/HHQ-67 The no-xlibs problem seems to pop up quite frequently. We have an existing bug open to better detect this condition: http://jira.hyperic.com/browse/HHQ-40 Glad to hear you both got HQ up and running so quickly!
Thanks for the pointer, John has updated the documentation: http://support.hyperic.com/confluence/display/DOCSHQ27/Install+Guide
The webapp name is derived using ServletContext.getRealPath(java.lang.String path). It's detecting the name as /webapp since that is the directory your webapp is deployed into. Even though the n... See more...
The webapp name is derived using ServletContext.getRealPath(java.lang.String path). It's detecting the name as /webapp since that is the directory your webapp is deployed into. Even though the name is not what you expect, the service is collecting metrics, right? If so, I'll look into what we can do to better detect the context name. What errors are you getting with monitoring the connectors? You are correct in that the configuration is showing up multiple times, but that should only be a cosmetic issue. I have logged this as http://jira.hyperic.com/browse/HHQ-66 Is there anything relevant in your agent.log?
I have just committed the new Resin plugin. The new plugin removes the need to deploy our hyperic-hq webapp. (It also requires that Resin is run with Java 1.5) It's a pure xml plugin, so y... See more...
I have just committed the new Resin plugin. The new plugin removes the need to deploy our hyperic-hq webapp. (It also requires that Resin is run with Java 1.5) It's a pure xml plugin, so you'll need to undeploy & redeploy to avoid duplicate server/service type exceptions. -Ryan _______________________________________________ hq-dev mailing list hq-dev@hyperic.org http://mail.hyperic.org/mailman/listinfo/hq-dev Message was edited by: rmorgan
Hi Dave, This is a known issue with the beta. The workaround is as follows: The VMware Virtual Mount Manager Extended service service is used by other VMware products, including VM Importe... See more...
Hi Dave, This is a known issue with the beta. The workaround is as follows: The VMware Virtual Mount Manager Extended service service is used by other VMware products, including VM Importer 1.x, DiskMount 3 (GSX), and DiskMount 5.5 (Workstation). If no other VMware products are installed, Virtual Machine Importer Beta should uninstall this service when it is uninstalled, but does not. Workaround: If you have no other VMware products installed, the VMware Virtual Mount Manager Extended service can safely be disregarded. If you prefer, you can stop the service, unregister it (enter "cd \Program Files\Common Files\VMware\VMware Virtual Image Editing" followed by "vmount2 /unregserver" at a command prompt) and remove the directory \Program Files\Common Files\VMware\VMware Virtual Image Editing. Thanks, -Alvin
Perhaps you will get a better response if you post this in the VM Importer Beta Forum. I will move it to that forum for you. BrianG - You friendly Neighborhood User Moderator
Were you able to successfully import the Ghost image as "a standalone VM"?
Virtual Machine Importer 2 Beta will not install on the same host as Virtual Center Beta 2. This is because the Importer Beta modifies a component that is also used by Virtual Center Beta, and w... See more...
Virtual Machine Importer 2 Beta will not install on the same host as Virtual Center Beta 2. This is because the Importer Beta modifies a component that is also used by Virtual Center Beta, and we did not want to introduce this variable into the Virtual Center Beta process. -Alvin
Also what platform are you importing to? Is it hosted (WS/GSX) or ESX?