Skip to main content

Lesson learned after the Azure bill is 2 times more than normal

Small things make the difference - Azure Billing Alerts 

In the last 3 months a part of the team was blocked with some urgent tasks. Because of this they didn’t had time anymore to review the Azure Services Instances that are running under the development and testing subscription.
The rest of the team didn’t check the costs and/or review the services that are running on Azure. In the context where the people that used to check this were blocked with other tasks generates cost that are 2 time more than the normal ones – even if only half of the team is working in this time period on development.

Of course the best solution was that somebody would check this and the responsibility to be passed to another person, but it didn’t happen. A better approach is to have a team that knows that running services on a cloud provider generates costs and they should all the time review what services they are using and turn off the ones that are not used.
But this didn’t happen of course.

There are 3 lessons learns from this story:

  • Cultivate inside the team - ‘responsibility’. People should all the time care about this thing and do this checks pro-actively (for the resources that were created and used by them).  
  • Identify and have all the time a person that is responsible to check the current bill.
  • Use Azure Billing Alert – It allows us to set an alert (email alert) that is send automatically to one or two emails address in the moment when the threshold

Azure Billing Alerts it’s a preview feature from Azure, that allows us to specify to send an email to maximum 2 custom different email addresses when the bill value reaches a specific value. In this moment this service is free and allows us to configure maximum 5 alerts.
We decided to configure 5 different alerts and different values.  We set a custom message to each alert that specifies that this is a real alert only if the alert is send before a specific day in the month. For example, it is normal to reach 100$ consumption after 4 days, but if after 1 day you already reach 100$ than you might have a problem.

What other ways to prevent this kind of situation do you see?

Comments

  1. There should be a setting to automatically cap/limit the resources used by a subscription to a maximum, at least for those scenarios where the budget is limited..

    ReplyDelete
    Replies
    1. Yes, you have this possibility. But you cannot stop the development for 10 days because the cap was reached.

      Delete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP