We are excited to announce the new Elastic Cloud usage analysis page. You can now explore and analyze your Elastic Cloud usage to better understand how the resources you consume contribute to your monthly bill. Your Elastic Cloud monthly bill consists of usage fees for the resources you used, including: Understanding your resource utilization allows you to make smarter decisions about your Elastic deployments as well as identify areas where you may be able to save costs.

We are excited to introduce Calico Cloud, a pay-as-you-go SaaS platform for Kubernetes security and observability. With Calico Cloud, users only pay for services consumed and are billed monthly, getting immediate value without upfront investment.

Driving productivity of software development and delivery teams is critical for any organization. The six years of research by DevOps Research and Assessment (DORA) showcases the role easy-to-use tooling plays in driving this productivity and in turn a better work/life balance for the team. The research finds that highest performing teams are 1.5x more likely to have tools they consider easy to use.

We give entrepreneurs from around the world the opportunity to build their projects with FlashDrive, and we're grateful to be able to give back to the startup community all the help we received when we launched FlashDrive not so long ago. FlashDrive Startups Program is a free program designed for startups at various stages that provides free computational credit and dedicated support to help startups quickly get started with FlashDrive's infrastructure, innovate, and grow rapidly.

Here at Lumigo, our mission is to help customers succeed with serverless by solving the observability problem and letting them focus on adding business value with serverless technologies. And to do that, we love to eat our own dogfood – be it using the same serverless technologies that our customers use and even using Lumigo to monitor Lumigo itself! That way, we feel your pain and we find solutions to problems that you care about.

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.

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.

Chaos engineering has definitely become more popular in the decade or so since Netflix introduced it to the world via its Chaos Monkey service, but it’s far from ubiquitous. However, that will almost certainly change over time as more organizations become familiar with its core concepts, adopt application patterns and infrastructure that can tolerate failure, and understand that an investment in reliability today could save millions of dollars tomorrow.

The future is bright for the cloud. In 2019, 90% of companies were already in the cloud and this impressive amount is expected to jump another 4% in 2021. And it gets even more interesting. By 2024, more than 45% of IT spending will edge out legacy networks and replace them with the cloud. As this reality unfolds, the result will be a long-term change in enterprise IT and supplier landscapes. It also means that knowing the cloud is part of the new normal of IT. What’s helping to drive these trends?

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.