Operations | Monitoring | ITSM | DevOps | Cloud

This blog explains a peculiar issue faced when Azure Durable Functions are deployed using Azure DevOps. In case you need to know what Azure Durable Functions are, please refer to Microsoft’s documentation on Durable Functions here as the explanation of it, is not under the scope of this blog. Durable functions work best when built with versions .NET Core 2.2 and above. After developing and testing a durable function, it can be deployed to Azure in many ways.

If you’re a gamer, you probably know how immersed you can get in your favorite game. Or if you’re the parent or partner of a gamer, you probably know what it’s like to try to get the attention of someone who is in “gaming mode.” Creating worlds and enriching players’ lives is in Ubisoft’s DNA.

We recently adopted NodeBB as our software of choice for building the Netdata Community. We have many good reasons for why we wanted to provide our community with a proper home online, but I wanted to cover some of the technical reasons for choosing NodeBB for our platform, and the many parallels between the NodeBB and Netdata projects, which was certainly a driving force behind this decision.

You’re ingesting 20,000 data points a second, in 400,000 metrics, from thousands of AWS instances – and your monitoring can’t handle the load. You need a scalable, highly-available monitoring and dashboarding solution (and you need it yesterday). Should you do it yourself with an in-house Graphite or Prometheus monitoring system? Or will you skip the headache and choose a hosted service like MetricFire?

One of the best things about cloud computing is how it converts technical efficiencies into cost-savings. Some of those efficiencies are just part of the tool kit, like pay-per-use Lambda jobs. Good DevOps brings a lot of savings to the cloud, as well. It can smooth out high-friction state management challenges. Sprucing up how you provision cloud services, for example, speeds up deployments. That’s where treating infrastructure the same as workflows from the rest of your codebase comes in.

All deployments are not created equal, but you'd never know it from your Slack channel notifications. In reality, some deployments you really care about, as they contain things like API changes or database migrations, and you want that information to surface. We created tags in Sleuth for this very reason. Out of the box, Sleuth matches files in your deployment with known patterns, and if any are found, tags your deployments automatically.

The community forum is a place where you can meet and chat with other Icinga users. It’s hosted by Icinga and moderated by both the Icinga team and members of the community. It’s mostly being used as a platform to ask and answer technical questions about Icinga, which is a great way to learn more about the tool stack! What does it look like? It’s a discourse platform, so it’s a collection of threads or topics which are open for anyone to leave a comment on!

Chief Architect at Drift, Freedom Dumalo, recently spoke with the CloudZero team about how they’ve successfully cut cloud costs by $2.4M in just a few months. When the world rapidly transitioned to work from home, Drift, the conversational marketing platform known for their chatbots, saw a spike in their customer utilization. The largest usage spike were among new users experimenting with their free trial. This increase in engagement was a great sign for their business.

After growing Carbon Black from nothing to over 800 employees, Founder and CTO Ben Johnson turned his attention to the security of SaaS applications with new startup Obsidian Security. Obsidian secures companies like Office 365, G Suite, Salesforce, Slack and Zoom. This time around, Ben is a seasoned founder and is proactively thinking about how to scale his company with healthy product margins. He uses CloudZero to monitor his AWS costs, detect anomalies, and enable his engineering team.