Operations | Monitoring | ITSM | DevOps | Cloud

As cloud technology has matured, hybrid and multi-cloud approaches have become commonplace. Enterprises have discovered that not all applications are suitable for the public cloud, meaning on-premise data centres are still active, and each public cloud has its own strengths and weaknesses, driving businesses to mix-and-match to suit their needs. This results in interoperability challenges for multi-cloud environments.

Enterprises today want real-time business insights to make decisions that improve operational efficiency and customer engagement and present newer revenue opportunities. However, the promise of the data-driven business falls short due to gaps in data management. These gaps exist because data in the modern enterprise doesn’t exist only behind firewalls and within organizational premises.

Organizations receive high monthly bills from cloud providers with no way of determining why the number changes from month to month or how to accurately predict future spend. More importantly, there is little information to provide visibility if cloud resources are being deployed efficiently or if spend is correlated to business performance.

Azure is the public cloud computing platform of Microsoft and it offers: Azure comprises more than 600 cloud services and supports varied operating systems, databases and developer tools. And the best part (in our opinion)? Splunk On-Call integrates with Microsoft Azure to help on-call teams improve incident response for Azure-based environments.

On the heels of several exciting developments about Splunk Cloud Platform announced at.conf22, I am excited to share today that Data Manager now supports onboarding of Microsoft Azure data sources, effective immediately.

Today I’m going to speak about another important Best practice, Tips, and Tricks that you need to know before you start to develop your Logic App solutions: Choose properly your developer tools.

In this blog post series, we will be comparing different services in AWS, GCP and Azure. We'll go into detail in each of the resources and understand the differences between providers, something you need to be aware if you are looking into switching clouds. Some examples will be given using Terraform, the Infrastructure as Code (IaC) market leader. If you want to know more about different IaC tools and how they compare, check our other blog post - Terraform vs Pulumi vs CloudFormation.

Amazon Web Services (AWS) provides three types of Elastic Compute Cloud (EC2) instances; On-Demand Instances, Reserved Instances (RIs), and Spot Instances. EC2 On-Demand instances are the default and most expensive instances. RIs and Spot instances offer discounts of up to 72% and 90% on On-Demand instances, respectively. The Reserved Instances are long-term commitments that guarantee you compute power for a year or three. Spot instances fluctuate in price and availability constantly.

Today I will talk about naming convention because I think this is so critical to implement from day one, and people tend to forget. We earlier addressed the importance of providing a good naming convention to your Logic App name and actions inside your business process. Today we will speak about the Connectors (or API Connections) naming convention.

Even though NoSQL databases like Amazon’s own DynamoDB are very popular today, for many business use cases, there’s almost no way around using a traditional relational database. Amazon Relational Database Service (RDS), released back in October 2009, is one of Amazon’s first cloud services and can therefore be seen as a very mature service.