Operations | Monitoring | ITSM | DevOps | Cloud

“Morning, mate,” I greeted Dinesh as he walked into the office. “Nice get up for the big day!” He was wearing a pressed shirt, rather than his usual hoodie. “Thought I’d make an effort, you know,” he grinned. We’d been planning intensely for this moment for the last week or so – our meeting with Charlie, the CIO, to present the results of our Moogsoft experiments and ask for permission to extend the rollout across the enterprise.

Since 2009, Juju has been enabling administrators to seamlessly deploy, integrate and operate complex applications across multiple cloud platforms. Juju has evolved significantly over time, but a testament to its original design is the fact that the approach Juju takes to operating workloads hasn’t fundamentally changed; Juju still provides fine grained control over workloads by placing operators right next to applications on any platform.

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 some challenges or limitations in managing and monitoring Azure Messaging resources using the above two.

In this series, we’ve introduced key HashiCorp Vault metrics and logs to watch, and looked at some ways to retrieve that information with built-in monitoring tools. Vault is made up of many moving parts, including the core, secrets engine, and audit devices. To get a full picture of Vault health and performance, it’s important to track all these components, along with the resources they consume from their underlying infrastructure.

In Part 1, we looked at the key metrics for monitoring the health and performance of your HashiCorp Vault deployment. We also discussed how Vault server and audit logs can give you additional context for troubleshooting issues ranging from losses in availability to policy misconfiguration. Now, we’ll show you how to access this data with tools that ship with Vault.

A few months ago, I was asked if I wanted to develop an open-source Terraform provider. Eleanor Saitta, principal at Systems Structure Ltd, had a client who was setting up JFrog Xray across their Github repositories but didn’t want to configure each repository by hand. As an SRE who enjoys working on projects that automate away those sorts of pain points (and someone who works extensively with Terraform during their day job), this sounded like an interesting project to work on.

Serverless computing is one of the fastest-growing areas in software development, along with hybrid clouds and using multi-cloud strategies. The global serverless architecture market is expected to grow at a CAGR of 16.2% in 2021 through 2026. It will reach $10.29 billion from $4.2 billion in 2020, according to MarketWatch. The serverless approach promises to help developers beat the cons of self-managed and even virtual server infrastructure. But is serverless right for you?

Last week DevOps Institute’s Chief Ambassador, Helen Beal, and Moogsoft’s own Chief Evangelist, Richard Whitehead, continued to follow the exploits of DevOps Engineer Sarah and her journey towards AIOps and Observability enlightenment.