Operations | Monitoring | ITSM | DevOps | Cloud

You're not alone if you have trouble visualizing, measuring, and controlling your IT costs. Whether public or private, cloud computing can add to the cost problem. That’s because cloud computing offers on-demand resources, so misconfigured infrastructure, an overzealous engineer, or a blindsided operations team can do something that leads to a surprise cloud bill at the end of the month. But not so fast. What is cost optimization, and why is it different from IT cost reduction?

Depending on your available resources, data analysis can take place at the edge or in the cloud, but businesses don’t need to choose one location over the other. There are benefits to giving the edge autonomy to collect, process, and act on data locally. Data replication helps maintain edge autonomy and makes it easier for users to get the data they need, where they need it.

Cribl.Cloud’s Summer 2022 release is now available in an AWS cloud near you! As part of this release, we are excited to share the features we have been building, including the latest Cribl product releases (Stream 3.5 and Edge 3.5). This release brings some much-requested features that will help customers increase their compliance, reduce overall costs, and deploy a more resilient observability data pipeline.

Most of us picture cloud security threats as bad actors in some hostile country. More often, it’s you and your coworkers. Talk about cloud security and you’re likely to discuss provider-focused issues: not enough security, not enough auditing, not enough planning. However, the biggest cloud security risks continue to be the people who walk beside you in the hallways.

Sometimes it may not be easy to debug Azure Functions deployed on Azure since we cannot do inline debug through the Azure Portal. An option for us is to write information to the Logs console in key parts of our code to get insights into what’s happening inside our Function. We can do that using the following sentence: Another option, especially if we are developing our Azure Functions inside Visual Studio, is to run the Function locally.

Google is the most popular search engine on the planet. And there’s a good reason for that: their search service is extremely thorough, clean, and comprehensive. Need to know something just “Google it”. But there’s a catch—when you use Google to learn, Google is also learning about you.

Honeycomb uses AWS Lambda as a core part of our query execution architecture; Lambda’s ability to quickly allocate lots of resources and charge us only for use is invaluable to keeping Honeycomb fast and affordable. Our total Lambda bill is easily accessible in the AWS Console, but how do we know which customers or application areas dominate this bill? How do we judge the cost of changes we make to our own software?