Your statement about the HQ server / agent communication not supporting SSL is false. All communication to the agent from HQ is done over SSL, and agents are optionally given the ability to communicate over SSL with the server.
This option was made available, since setting up an SSL connection can be CPU intensive, and not all users care that their incoming metric data is visible.
Latest convergence headlines from Network World:
Akhter announces frugal 55 watt PC
Oracle technical forum upgrade plagued with problems
Two gaming powerhouses from ATI
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
You're right-- SSL is available
We apologize for omitting this fact. The problem, as we see it, is that SSL isn't turned on by default-- and it should be. Important management information shouldn't be clear text; it's too easy to dry rip the wire these days.
SSL available and complexity.
... I'd point out that, when I installed one version of this late last year at a client site, that Hyperic had actually released a version with broken SSL support - I had to turn SSL off on the local network to get the agents communicating with the server (after having enabled it in the previous version). How in the world this slipped by their Q/A is beyond me.
Regarding complexity: eventually, we wound up deploying another product, because HQ was overkill for our needs, and the time and energy required to utilize it to its full potential just wasn't available. We all thought it was a neat product. Just too much work to make use of for simple network monitoring.