Operations | Monitoring | ITSM | DevOps | Cloud

How can creating chaos achieve better reliability? Chaos and reliability might seem mutually exclusive, but through the use of Chaos Engineering, SREs can bring about meaningful changes to system resiliency.

Continuous monitoring (CM), also referred to continuous control monitoring (CCM), is an automated process that allows DevOps teams to detect compliance and security threats in their software development lifecycle and infrastructure. Traditionally, businesses have relied on periodic manual or computer-assisted assessments to provide snapshots of the overall health of their IT environment.

We all want to develop everything super fast. So, when something like a “simple” database sync process takes ages, we need to think outside the box. Here are the solutions we implemented, in JFrog Xray, to improve our DB performance, reducing the sync time from 16 hours to 2 hours!

Today’s IT landscape is complex, hybrid, and fast-moving, and the adoption of multi-cloud infrastructure, applications, and new digital transformation initiatives is accelerating. IT operations teams, playing a vital role in enabling the delivery of uninterrupted services and creating business value for enterprises, are finding they need to constantly grow their resources to manage all the moving pieces in their IT stack. This can get expensive … but how much are they spending?

“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.