Operations | Monitoring | ITSM | DevOps | Cloud

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.

As more and more of the public sector enact large-scale digital transformation initiatives, government organizations must find new ways to manage massive amounts of data securely while maintaining compliance. With new mandates from the Biden administration to enhance cybersecurity best practices in both the private and public sectors, organizations like the Department of Defense (DoD) face new challenges to their data management and communication practices.

Managing incidents is already tricky enough, and you want to get to mitigation as quickly as possible. But sometimes it feels like organizing everything surrounding an incident is more difficult than solving the actual technical problem and you end up getting delayed or sidetracked during mitigation efforts. We call that scenario the “people problem” of incident management.

A pull request (PR) is (quite literally) a request to pull a change into a project’s code or documentation. It is a popular change management process supported by many VCS providers including GitHub, GitLab, Bitbucket, Codeberg, and others. Typically these come with features to track open pull requests, tools to assist in reviewing the changes, the ability to approve—or reject—PRs, and finally to merge approved PRs.

IT admins are expected to keep the organization’s network reliable and resilient all while the complexity of today’s networks grows. From adopting hybrid infrastructures and maintaining multi-cloud environments’ security to managing ever-increasing bandwidth demands, enterprise network management is getting more difficult by day.

In this article, we will deploy a clustered Prometheus setup that integrates Thanos. It is resilient against node failures and ensures appropriate data archiving. The setup is also scalable. It can span multiple Kubernetes clusters under the same monitoring umbrella. Finally, we will visualize and monitor all our data in accessible and beautiful Grafana dashboards.

Did you know that data centers are some of the most energy-intensive buildings? They consume 10 to 50 times the energy per floor space of a typical office building. As governments, industry regulators, and customers demand more energy efficient data centers, data center managers are tasked to comply with corporate sustainability initiatives by finding new ways to innovate and reduce energy consumption.