The focus of this blog is to introduce a new set of capabilities coming to BindPlane, Blue Medora’s unique cloud service, which integrates AWS and Microsoft Azure services seamlessly with Azure Log Analytics for multi-cloud monitoring. No one in the market can do this today.
AWS and Azure cloud siloes
AWS offers a wide range of services including networking, analytics, application services, and deployment. Microsoft offers services like messaging, media services, CDN, and machine learning.
The range, complexity, and diversity of service offerings from AWS and Azure is attractive to enterprises and drives them to adopt multi-clouds as each offers specific application advantages. For example, Azure might be attractive for media services and messaging over AWS. But the ability to monitor diverse services across clouds on a single performance management platform remains as a challenge.
Multi cloud monitoring risks
Organizations leverage almost 5 clouds on an average2. According to RightScale, 81% of enterprises have a multi-cloud strategy2.
The widespread adoption of multiple cloud resources by enterprises is largely driven by siloed use cases, application specific migrations and independent business initiatives. Seldom is multi-cloud adoption driven by a unified cloud architecture. As a result, various teams throughout the IT organization manage these disparate resources with disparate tools, delivering fragmented observability at best.
- Siloed monitoring is unproductive
- Enterprise central IT teams are shifting their role to governance and brokering cloud2. Siloed IT teams will prevent central IT to successfully govern as they may not be in sync with corporate IT business alignment.
- When siloed business units enter into contract with different cloud providers and do not notify central IT they increase MTTR when a problem occurs.
- Operations management is one of the key cloud governance models3. Key risk is not having visibility into multi-cloud performance metrics due to siloed monitoring.
- Cloud hopping between AWS and Azure
Depending upon the enterprise application mix, platform technology, development environment requirements, availability, scalability, security, compliance, and performance needs, workloads can be migrated frequently between AWS and Azure – cloud hopping is a reality.
- Cross cloud siloed monitoring risks
Your central IT service delivery strategies should define what applications, services and related infrastructure go into which cloud provider (or multi-clouds) and when they should be migrated by the central IT team. The table below details several cross cloud monitoring risks.
|IT service delivery strategy
||Monitoring risks to consider
- You may operate the entire production applications or workloads on Azure and/or AWS, including customer user interfaces, compute and data processing/archival, and storage
- Consider the risk of central IT not having the topology view (see all objects) of workload distribution across clouds on Azure Log Analytics when cloud hopping
- Consider incident response in the event of loss of cloud service and strategies to fall back or switch clouds
- Use cloud/s for your development, test, and failover/recovery workloads and operate production applications using on-premise software and infrastructure
- Consider the risk of not being able to manage alerts in one place, including those generated by AWS services on Azure Log Analytics
- Use cloud only when your on-premise applications/servers need additional compute, network, and storage during periods of peak demand
- Consider the same risk as in strategy 1, but risks are limited to periods of peak demand
- Use multiple clouds simultaneously – use Azure for SaaS and PaaS and use AWS for IaaS. Use these clouds during early release cycles as features are evolving and when demand spikes
- Consider the risk of making capacity planning calculation errors (moving workloads) due to context switching between Azure Log Analytics and CloudWatch – no single pane of glass
- You may either merge/spinoff a new business unit or buy a company and let the unit run workloads/applications on its choice of cloud
- Risk of central IT not having full visibility across heterogeneous stacks from new business unit
- Risk of finger pointing between central IT team and siloed IT/management teams from new unit acquisition or spinoff when a problem or a service issue surfaces – this leads to higher MTTR
The new story – Azure Log Analytics for AWS and Azure
The time has come to transition from traditional siloed monitoring to unified monitoring by using a single monitoring platform like Log Analytics, enhanced with multi-cloud visibility. A single pane of glass for AWS and Azure will provide complete visibility to your central IT team and helps manage and optimize resources efficiently.
BindPlane – Purpose-built monitoring integration
BindPlane is the only pure MIaaS available—monitoring integration as a service that is open, extensible, simple and secure. BindPlane connects operational, performance monitoring, and brokerage insights from AWS services to Azure Log Analytics.
Key highlights and properties
- Seamless integration: Monitor your AWS resources on Azure Log Analytics – single pane of glass
- Dimensional data: Deep monitoring data based on expertise and enterprise knowledge base, imbued with relational visibility across the AWS IT stack
- AWS Services covered: EC2, EC2 Container Service, RDS, S3, Redshift, DynamoDB, Lambda, Elastic Beanstalk, Elasticsearch, and Kinesis
- Exposes performance and configuration related metrics, plus computed metrics while Amazon CloudWatch just exposes raw performance data for AWS services. Shortly after early “Preview” access is completed, 2507 metrics across 37 AWS services will be exposed. Google Compute Platform and IBM Softlayer will also be added soon
- Intelligent data collection: Agentless smart collector with AWS service discovery and touchless management
- Operational dashboards: 10 use case specific dashboard templates deliver dimensional data in operational context for relational visibility across AWS services
- Unified monitoring: React to issues faster and reduce operational friction by eliminating observability tool-sprawl
- Root-cause resolution: Full multi-cloud visibility for faster root-cause analysis
- Collect Azure and AWS alerts in one place – stay a step ahead to reduce MTTR
- Consistent dashboard digital experience across AWS and Azure services on Azure Log Analytics
- Enables Log Analytics to provide continuous visibility into AWS services so that you can
- Optimize workloads across different pricing models to achieve the lowest cost between Azure and AWS
- Continuously broker deals between Azure and AWS clouds to balance workloads and to clean up unused resources
- Saves time: IT Ops and DevOps can offload expensive and non-core AWS monitoring integration CI/CD time cycles. Azure Log Analytics users don’t need to invest time configuring, deploying and maintaining AWS integrations – No need for in house development
- Reduces TCO: Continuously updated monitoring data collection software that is always current with AWS services and related monitoring APIs, whether data collector is in the cloud or datacenter
Get started today
You can preview Multi-cloud monitoring for Azure Log Analytics today. Apply for limited early access to BindPlane and get a personalized demo.