Recently I’ve published a document on extending Microsoft and Oracle monitoring technologies. This is something which comes frequently in client interactions with a growing investment in Microsoft, Oracle, and VMware stacks. These products can be extended, but should be done with care, understanding where it makes sense and where overextension can occur. The research includes an extensive listing of 3rd party components and discussion around how these offerings can augment existing strategies. This includes solutions from : Microsoft, Oracle, VMware, Bridgeways, eG Innovations, Quest, Cisco, Dell, Fujitsu, HP, IBM, Comtrade, Citrix, Veeam, Brocade, EMC, NetApp, Solarwinds, BlueStripe, OZSoft, Realtech, F5, Savision, Entuity, and Blue Medora.
Hasn’t been much in terms of research or blogs the last 4 weeks, but I have been head down in a lot of new content regarding the monitoring space.
I’m close to also publishing an extensive research note targeted at SMB monitoring around lower cost and free monitoring solutions on the market. Soon after that I will be publishing some collaborative research on the future of application performance monitoring (APM) and content delivery and optimization (ADC/CDN). Soon after that more collaborative research will be published around the failures of capacity planning. All of these research notes should be out within the next 3 weeks, and additional research is forthcoming around the network monitoring space, virtualization management, and SaaS usage within IT.
Look for more content and blog posts soon.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.