Operations | Monitoring | ITSM | DevOps | Cloud

A foundational component of monitoring Google Cloud environments with Datadog is our Google Cloud Platform integration. This integration continuously collects metrics from all of your Google Cloud services and enriches them with tags, enabling you to scope dashboards and monitors to the relevant resources and seamlessly pivot across logs, metrics, and traces inside the Datadog platform.

Azure is a cloud computing service created by Microsoft to help businesses tackle challenges and build solutions through a comprehensive suite of cloud services. It offers a wide range of integrated cloud services and functionalities such as analytics, computing, database, mobile, networking, storage, and web, allowing developers to pick and choose from these services to develop and scale new applications, or run existing applications, in the public cloud.

In this article, we will see how we can integrate an Azure data source with Graphite and Grafana. This will allow us to monitor metrics from the applications hosted in the Azure cloud on a Grafana dashboard. We will also see how to integrate Azure Active Directory with MetricFire’s Hosted Graphite and Grafana. You don’t need fully functional cloud services running with Azure to understand this article, but it assumes that you have basic familiarity with Azure Cloud.

With data being the cornerstone of organizational growth, your data management strategy is integral to your business's success. Data is valued as much as human capital in today's business world: both are key factors contributing to the overall productivity of a company's strategy. Companies have to take simple steps to collect, manage, and analyze various data to run their operations successfully and efficiently.

Welcome to the forefront of virtualization technology, where innovation meets practicality, and the quest for optimal performance is a constant journey. If you’ve been keeping a close eye on developments in this space, you’ll know that Microsoft’s Hyper-V has been making significant strides.

In the last two blog posts, we explain how to specify nullable and required elements/properties inside our JSON messages. Today we will continue on the same topic, JSON Schemas. This time I will speak about another Best practice, Tips, and Tricks that you must consider while designing your business processes (Logic Apps): Specifying JSON Schema restrictions.

In the realm of virtualization, snapshots play an integral role in managing virtual machines (VMs). Essentially, a snapshot captures the state of a VM at a specific point in time, providing a reference point to which you can revert if necessary. This can be especially handy when implementing changes to your VM or its applications, allowing you to quickly undo the changes if they cause any unforeseen issues.

Cloud security is a constant concern and tends to revolve around common themes - how do you give intended users access to the data and systems their clearance allows, while maintaining a good user experience; and how do you keep unintended users or malicious bots out? In the entanglement of systems, services, and applications that make up a modern IT infrastructure, this is a lot harder to balance in practice than it is on paper.

In the last post, we explain how to specify nullable elements inside our JSON. Today we will continue on the same topic, JSON Schema. This time I will speak about another Best practice, Tips, and Tricks that you must consider while designing your business processes (Logic Apps): Specifying JSON Schema required elements.

In case you missed it, AWS experienced an outage or "elevated error rates" on their AWS Lambda APIs in the us-east-1 region between 18:52 UTC and 20:15 UTC on June 13, 2023. If this sounds familiar, it's because it's almost a replay of what happened on December 7, 2021, although that outage was significantly more severe and took longer to restore.