A full overview of the best ways to monitor Azure. Opsview Monitor comes with 9 Azure Opspacks, with more to come in the future.
You are here
Monitor Azure Resources with Ten New Azure Opspacks
Ten new Azure Monitoring Opspacks!
Opsview Monitor now provides enhanced ability to discover and monitor Azure resources and business services under a single pane of glass with everything else in your global hybrid IT estate.
The nine infrastructure-oriented Azure Opspacks included with Opsview Monitor 6 Early Adopter Edition (Azure has been supported since Opsview Monitor 5.x) have this week been amplified with release of ten new Azure Opspacks for version 6, covering critical network components, storage, container hosting, and the ability to monitor the health of specialized server instances for analytics, API management, app services, and service plans. Users of Opsview Monitor 6 will need to download and apply the Opspacks in order to use them (the next release of Opsview Monitor will include them out of the box).
Additional Azure Opspacks for Opsview Monitor 6 will be released in coming weeks, so stay tuned! As always, all Opspack code is open source and fully Opsview-supported for customers.
Users of Opsview Monitor 6 can download and install the new Opspacks directly from our website, or from our GitHub repository (downloadables are available from the ‘releases’ tab of each sub-repository -- here’s an example of what you’ll find there).
Seamless monitoring via Azure APIs and instrumentation!
The new Azure Opspacks ingest data directly from Azure’s built-in monitoring API and instrumentation. This lets you monitor Azure hosts and services quickly and non-intrusively -- viewing them alongside on-premises IT resources (and resources residing in other public clouds) under Opsview Monitor 6’s single pane of glass.
Want to run Opsview Monitor on Azure? No problem!
Opsview Monitor can be deployed on premises or in any cloud, including Azure. It can monitor your Azure resources remotely (and securely) via a site to site or point to site Azure VPN connection. Alternatively, you can deploy an Opsview Monitor Collector node on an Azure VM. The ability to deploy in your own datacenter or in the monitored cloud can solve bandwidth/cost bottlenecks that can potentially make detailed monitoring of very large Azure resource pools expensive or impractical.
Try the new Azure Opspacks! Here are links to the new Azure Opspacks. In the next two weeks, we’ll be providing some tutorials and lab reports on how to use them to keep your Azure cloud estate humming!
All About Azure
While Amazon Web Services (AWS) still owns the lion’s share of enterprise cloud business, Microsoft Azure is coming right along. Two stellar quarters of revenue growth (Q4 2017 - 97% and Q1 2018 - 89%) saw Azure at midyear with 29.4% of cloud workloads -- dwarfing the 20% long tail led up by Google (3%), Rackspace, and other providers (according to a July 2018 Cloud Security Alliance report, available free as a download from McAfee Software).
Azure is catching up for good reasons -- reasons that go beyond being a more Windows-friendly public cloud with fully integrated, hosted Active Directory -- great for onboarding enterprise Windows customers and smoothing their hybrid cloud transitions. Azure’s web portal and embedded Bash or PowerShell-based management CLI are easier than competitors’ to use. While the total scope of services offered isn’t as staggering as Amazon’s portfolio, the latest tech is all in place -- DBaaS, FaaS, VPNaaS, Kubernetes/Docker, serverless functions, etc. So is strong integration with Visual Studio team development.
More like this
Opsview has introduced the Opsview Puppet Module, which automatically registers compute instances for monitoring within Opsview Monitor.
Kubernetes’ extraordinary resilience tends to change the emphasis of monitoring from alerting to resource and performance management.