Operations | Monitoring | ITSM | DevOps | Cloud

A look at outages and disruptions to the IT systems that power the Olympics, from 1996 to today.

As the adoption to cloud expand, subscribing and provisioning resources increases day by day. Enterprises have multiple strategies to implement their cloud deployments: single cloud, private cloud, multi-cloud, or hybrid cloud. There is a need to analyse and assess on regular basis to keep a watch on the usage to ensure expenditure on the cloud resources are efficient and there is no wastage. There are various possibilities but will need some level of technical competence and regular maintenance.

In any integration solution, when many Azure services come together to communicate with each other, there is a need for the organizations to build an end-to-end traceability/monitoring solution that can be used by the business users and IT support. Perform end-to-end message tracking and capturing necessary data on business process flow across Azure resources and hybrid integrations. Consider an organisation that has a well-defined Employee Onboarding process.

From containerized workloads to microservice architectures, developers are rapidly adopting new technology to scale their products at unprecedented rates. To manage these complex deployments, many teams are increasingly moving their applications to third party–managed services and infrastructure, trading full-stack visibility for simplified operations.

When you migrate workloads from on-premise infrastructure into a public cloud, you can improve the performance, reliability, and security of your application, and you might also lower your costs.

Do you author plans for Puppet Enterprise? Looking for ways to improve them? Read on! The Puppet Plan language allows a variety of methods to pick targets. In this article we will explore two of these methods (TargetSpec parameters and PuppetDB queries) and how plan authors can employ the latter to: Note: the following examples assume that you are running against targets that have the Puppet agent installed.

Buying software is often the answer for busy engineering teams in search of a quick solution with minimum aftercare. But while your team may be sure of the problem, how do you go about searching for a product to fix it? Far from being the 'easy option', there is a lot you need to consider before you invest in a bought solution – user experience, cost comparisons, and support features to name a few. Let’s explore some of the considerations when making a good decision.

Towards the end of 2016, it all started with developing a simple platform to manage Microsoft Azure Service Bus namespaces. The then classic Azure portal had limited capabilities to manage Azure Messaging resources like Service Bus Queues and Topics. Paolo Salvatori developed and managed a community tool called Service Bus Explorer. We identified that there are challenges or limitations in managing and monitoring Azure Messaging resources using the above two.