Skip to main content

Azure Development Environment - Control the bill


Azure Development Environment Series:


When you have a development team that is working on an application that is hosted (or is using) on Azure you need to be aware of the costs that are generated by Azure Services.
Even if the costs can be low at the beginning, if you have a big team the costs can increase. For example if one developer needs 3 Worker Roles, 2 instances of SQL Azure and 2 different namespaces of Azure Service Bus you can have a monthly costs of 100 EUR. But if you add 6 more people, you will add automatically another 600 EUR at your bill.

Review Azure Bill
To be able to control these costs, you should have a person that is responsible to check the Azure bill every month. This person should not look only at the final cost, but it should look on what services are generating the costs and try to drill down on the most expensive one or the ones that increase too much from one month to another.
It is important to be aware that the scope is not to identify the person that generates the extra costs. More important is to understand why the extra costs is generated and if it is normal or not.
You can make an idea of the usage and the cost of each service usage directly from the billing portal.


How to analyze Azure Bill
The new report that is generated from the billing portal contains a section called 'Statement'. This is the first section that we should analyze. I usually order this section by value and extract the top 5.



Once we do this, we can investigate further, each of them in the next section of the report, that contains also the instance name of the resource that generated the cost, when and so on. Based on this data we can find out easily what generated the costs.


In the above example I filtered the results to see only the Service Bus resources. The last column in the right contains the name of the namespace (service) that made the consumption.
More about this can be found here: https://azure.microsoft.com/en-us/documentation/articles/billing-understand-your-bill/

New Portal
The new portal gives us the ability to see a chart with the current bill, splitted on the type of the service that generated the cost (Compute, TH, ...).

There is also a burn chart that can indicate you that the costs are increasing too fast.

Both reports are useful, but they provide you only an overview. If you want to find more information about what generated the cost you will need to use the Usage Details report that contains all the information that are necessary to identify what generated that costs.

Azure Alerts
This is one of the most important thing that you should do if you don't want to have surprises. From the billing portal we can define alerts that can be sent automatically when the total billing reaches a specific value.

In this way, you can take actions before a disaster and control the costs. This feature is in preview mode, you should activate it if you want to play with it - https://azure.microsoft.com/en-us/services/preview/

Tracking
To be able to track more easily what resources are created by each team member, you can use prefix in front of the name of each service instance. The prefix can be the initials of the team member.
For example in my case it would be (Radu Vunvulea - rv):

  • rvdemostorage
  • rvsbtestnamespace
  • rviotstorage
Conclusion
You should always track the billing costs and know what are the services that are generating the costs. Also, try to find methods that would allow you to track the purpose of different resources. A resource named 'abc' would not help you.



Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…