Operations | Monitoring | ITSM | DevOps | Cloud

Whether you’re a national business with sites across the country, a global enterprise with operations in multiple markets, or a SaaS provider looking to roll out in new geographies, interconnection is essential for connecting to customers and partners.

Over the past few years, Microsoft Azure has seen tremendous growth, and many new enhancements have improved user productivity. To keep users well informed about their resource status and availability, Microsoft has also been actively working on various monitoring capabilities.

The planning of an IT automation project is crucial to success, this article takes a deep dive into areas which should be considered and addressed before embarking on an automation journey. Securing executive sponsorship and establishing governance Having the support and guidance from a senior leader within your organisation will undoubtedly benefit the delivery of your project. Implementing automation is change, and as with any change; has the potential for resistance.

In this episode of Coffee & Containers, North American DevOps Group‘s Jim Shilts speaks with Shipa‘s Bruno Andrade, VMware Tanzu‘s Gautham Pallapa, and IBM Cloud‘s Jason McGee McGee.

HAProxy publishes more than 100 metrics about the traffic flowing through it. When you use HAProxy as an API gateway, these give you insight into how clients are accessing your APIs. Several metrics come to mind as particularly useful, since they can help you determine whether you’re meeting your service-level objectives and can detect issues with your services early on. Let’s discuss several that might come in handy.

When it comes to reputational risk, a reactive approach is generally taken by organizations, with efforts focused on handling threats to their business they are already aware of. As much as this enables short term damage limitation, it may not be enough to manage and protect your risk in the long term. Instead, a more proactive approach is key to success.

As a cloud cost intelligence company, we often like to say “every line of code is a buying decision”. If you’re running on AWS or one of the other big cloud providers, you know that a simple decision about how to architect an application can have a significant impact on your future cost of goods sold (COGS). However, in my experience, many engineering teams don’t discuss cost — at least not until it’s already become a problem.