Applying consistent tags to your cloud resources can help improve the way you organize and manage your cloud environment. For example, tagging based on environment and application enables you to quickly identify all production resources supporting a specific application. Maybe you want to target automation processes at these resources or exclude them from a specific access role. Tags enable you to do that easily and manage your cloud environment in a way that makes sense for your business.

In a previous post, I talked about the potential of AIOps and why true AI (Artificial Intelligence) hasn’t had much impact in the monitoring space yet. However, I believe Algorithmic IT Operations can help and will share the path LogicMonitor is taking to get there in this post.

Google Cloud Platform’s (GCP) Cloud SQL is a managed MySQL and PostgreSQL database service. This service enables you to quickly set up and manage databases for your applications without having to maintain the underlying infrastructure.

A recent study from Mulesoft shows that 75% of enterprises have moved past the digital transformation planning stage to rolling up their sleeves and diving into implementation. Teams are updating their IT Operations Management (ITOM) strategies, moving more systems and services to the cloud, and automating tedious manual processes that have historically been the root cause of migraines for many people.

Terraform is an open source orchestration tool for provisioning, managing, and versioning cloud infrastructure. Terraform uses a configuration file as a blueprint of the desired infrastructure state, and changes the target environment by updating or creating resources to match the defined state. Having a defined outline of your datacenter and following this “infrastructure as code” model allows for repeatable automation.

LogicMonitor’s LM Cloud now offers support for monitoring Azure cloud spend (in addition to detailed AWS cloud spend). We’ve made it easier than ever to monitor cloud costs and control them. LM Cloud utilizes Azure’s Rate Card and Usage APIs to calculate Azure billing data and break it down in a meaningful way. By default, cost is monitored per subscription, per region, per service, and per operation, with the ability to enable monitoring per tag as well.