Operations | Monitoring | ITSM | DevOps | Cloud

These three top cloud providers are used daily by millions of users across the world – but what sets them apart? We take a magnifying glass to the features that matter.

KubeCon is the major cloud-native gathering of thousands of people from around the globe. The event is attended by many emerging startups and companies working on revolutionary products around Kubernetes, security, containers, and DevOps. It is a great opportunity to share insights and collaborate on various community projects.

Mend is an automated vulnerability scanning tool that helps teams detect and resolve issues quickly. Mend can discover outdated packages and tell you if you’re relying on tools with known issues. Then, through automated remediation, Mend creates pull requests for developers with specific guidance on resolving those issues. Mend conducts static code analysis as well as package and dependency management analysis to identify weaknesses.

High-quality cloud cost allocation has become an existential issue for businesses. In order to get as much out of their (mounting) cloud investments as possible, business leaders need to know how much they’re spending in the cloud, what/who they’re spending it on, and whether there’s a good reason for it. In its ideal form, cost allocation answers all these questions.

For a successful business, you need to introduce an effective monitoring system covering all areas of your business and infrastructure - servers, databases, services, overall traffic, and even revenue collected. The users of this monitoring system can be system administrators, software engineers, information engineers, as well as all sorts of analysts.

In this podcast, our panellists discuss the foundations that any team needs to put in place when designing their incident management process. Starting from the basics of defining what we really mean by an incident, to how to set your severity levels, roles and statuses, Chris and Pete share their tips for building solid foundations to run your incidents.

Why do some organizations excel in streamlining their database operations and applications development while others find it immensely challenging? Why can some database teams embrace agility while others take months of cycles to deploy even a single line of code? What secret sauce can allow some database teams to work smarter (not harder), streamline database development lifecycles better, get to deployment faster, and create an overall stronger alignment across departments?

As a former incident responder and now as a responder advocate for FireHydrant, I’ve seen the “build vs. buy” debate play out many times. In fact, I even supported the tool that former employers used for managing incidents for years before they decided to buy (more on that in a future blog post).