Operations | Monitoring | ITSM | DevOps | Cloud

Delivering great performance and reliability for your critical applications just keeps getting harder, doesn’t it? Between microservices, mercurial cloud resources, containers spinning up and down, distributed teams, specialized teams, and developers making changes, it’s an increasingly complex environment. With so many moving parts, if something goes wrong, how do you know what happened where, and what your environment looked like at the precise moment the problem began?

Welcome to the Cloud 66 Changelog. These are the changes that have gone out this month.

The CPU attack is one of the most common attack types run by Gremlin users. CPU attacks let you consume CPU capacity on a host, container, Kubernetes resource, or service. This might sound like a trivial exercise, but consuming even small amounts of CPU can reveal unexpected behaviors on our systems. These behaviors can manifest as poor performance, unresponsiveness, or instability.

Robocalling is no small problem. These nuisance calls are the major source of consumer complaints, with some estimates suggesting that more than 22 billion robocalls have been made in 2021 alone – and we’re only halfway through the year.

As we know, the Covid-19 has a drastic impact on almost every industry including healthcare organizations, where the health care workers and healthcare teams are bearing the heaviest impact from this pandemic. Moreover, the pandemic transformed the way healthcare organizations approach care team collaborations and interactions with the patient.