If I create an Azure cloud services (implemented using .NET Core in my case), is there a way to get an estimation of the resources needed for the service BEFORE (not analyzing it after the fact) it is deployed to the cluster? By resources I mean number of cpus needed, memory being used etc.
Before deployment any application We can use Azure pricing calculator to analysis our uses and cost as per our requirement .
And alternatively based on the MS DOC we can review estimated costs according to our requirement tool in the Azure portal:
When you create an App Service app or an App Service plan, you can see
the estimated costs.
To create an app and view the estimated price:
On the create page, scroll down to App Service plan, and click Create new.
Specify a name and click OK.
Next to Sku and size, click Change size.
Review the estimated price shown in the summary. The following screenshot is an example and doesn't reflect current pricing.
For more information you can refer this MS DOC: Sizes for Cloud Services
Related
I have been following the learning path for Microsoft Azure AI 900. In the second module, I have deployed my model as an endpoint. It says Container instances for compute type. How much will this cost me. Azure doesn't seem to show any pricing for this. Is this endpoint always active? If yes how much does it cost?
The price depends on the number of vCPU and GBs of memory requested for the container group. You are charged based on the vCPU request for your container group rounded up to the nearest whole number for the duration (measured in seconds) your instance is running. You are also charged for the GB request for your container group rounded up to the nearest tenths place for the duration (measured in seconds) your container group is running. There is an additional charge of $0.000012 per vCPU second for Windows software duration on Windows container groups. Check here Pricing - Container Instances | Microsoft Azure for details
After Deployed the Azure Machine Learning managed online endpoint (preview).
Have at least Billing Reader access on the subscription where the endpoint is deployed
To know the costs estimation
In the Azure portal, Go to your subscription
Select Cost Analysis for your subscription.
Create a filter to scope data to your Azure Machine learning workspace resource:
At the top navigation bar, select Add filter.
In the first filter dropdown, select Resource for the filter type.
In the second filter dropdown, select your Azure Machine Learning workspace.
Create a tag filter to show your managed online endpoint and/or managed online deployment:
Select Add filter > Tag > azuremlendpoint: "< your endpoint name>"
Select Add filter > Tag > azuremldeployment: "< your deployment name>".
Refer here for more detailed steps
I have function app which process XML files from Azure blob and put the data in Azure SQL DB. This is working fine when the Size of the file is in kb ( we have told the sender to send the file up to 100kb).
The problem comes when the file size increases to “2MB to 3MB”. The problem is it gets stuck in middle of processing and as the job runs in every 2hours, the blob receives files in every 2 hours - then everything stuck ( the current processing files and the new files as well )
I can’t change the schedule from 2hours to more. considering this, Is there anyway to scale up or scale out the app service plan so that it can process the larger size in 2hours time? Will there be a code or configuration change required for this ? Also, if yes, what is the costing plan for this?
Or, is there any other way to handle such situations?
Please note, the current app service plan is S2:2 and all deployment slots are in same app service plan.
Thank you Roman Kiss and Anupam Chand. Posting your suggestions as answer to help other community members.
The hosting plan you choose dictates the following behaviors:
How your function app is scaled.
The resources available to each function app instance.
Support for advanced functionality, such as Azure Virtual Network connectivity.
Check Hosting Options for further information.
Here is the pricing calculator for moving P1V2 to P1V3.
Below image will help you in scaling up your app service
If you app depends on other services like SQL and Storage you need to Scale up these resources separately.
In the Resource Group link go to summary and select the resource to scale up.
For further information click Scale up in Azure App Service.
in my Azure architecture I would like to scale down a couple of web app services.
I would like to use the D1 tear, which has a limited consumption time of 240 min/daily (as you can see in the picture below).
My question is: how can I use the Azure Monitor Metrics tool to get the average compute time for the last 30 days?
Maybe the CPU Time?
I'm asking that because I don't know if those web services work less then 4 hours a day.
Thanks for reading
Thanks for asking question! You may want to know that Azure App Service provides built-in monitoring functionality for web apps in the Azure portal from the Azure portal, you can review quotas and metrics for an app and App Service plan, and set up alerts and autoscaling rules based metrics.
If the app is hosted in D1 that is Shared plan, the limits on the resources that the app can use are defined by quotas.
Check Understand quotas and Monitoring quotas and metrics in the Azure portal
Let us know if further query.
There's an awful lot of disjointed documentation on monitoring network/resources in Azure. What I'm looking for is which pieces are needed to get information from VMs, NVA firewalls, azure load balancers, and other network resources and network connectivity into a single pain of glass in Azure. Only concerned about Azure, not on-prem for now.
I've come across azure monitor, log analytics work spaces, event hub, vm extensions, network watcher, insights, etc...but I'm not sure which are required and which are not. One doc leads to the next and I end up with 30 tabs open. I'll also need to be able to push logs to other security devices such as a SIEM.
Does anyone know of a deployment guide that wraps this all up in a more logical fashion? Does anyone have any feedback on which pieces from azure (not 3rd parties) are required at a minimum to accomplish a single pane of glass to view my Azure environment holistically?
General overview of observability in Azure
Likely, the thing you're looking for is Azure Monitor. It's an umbrella term for everything observability related inside Azure.
To store Metrics and Logs you need Log Analytics: it can query data with kusto query language, visualize results, define Alerts on queries.
Alerts is quite a complex beast, as it is spread across the entire cloud. Two types that I use the most:
log-analytics alert (which I mentioned above)
Alerts tab, which is available at every Azure component view. for example, open resource group, and scroll down to Monitoring section
Each component also has a subset of built-in metrics. Likely, you noticed that many azure components on the Overview view display some charts. For example, Azure Storage Account displays Total egress, Total ingress, and other line-charts. When you click on these charts you can customize them. These metrics and charts are free to use.
Microsoft also has all-in-one observability solution for Azure Functions and Web Apps: Application Insights
Dashboards allows to join multiple charts into a single view and share it with others.
If you care about security, Azure proposes Azure Security Center
Deployment/management strategy
I suggest to start with:
Create Log Analytics Workspace, which is the storage for metrics and logs. The azure docs article explains how to design it: how many instances to use, how to rate-limit ingestion (it might be expensive if goes out of control), how to access it and so on.
To get Azure components logs, look for Diagnostic Settings tab at a component page at Azure portal, but not all components has it (sic!). I suggest
sending the most critical data to Log Analytics workspace to store them in a queryable format for 30 days (it's in free tier). This is needed for investigating current issues with your infrastructure
if you might need logs later than 30 days - send them to Storage Account
you mentioned SIEM integration - route required events to Event Hub and then process the stream according to your requirements
So, if you need long-term storage - you need to create Azure Storage Account.
If you need real-time analysis - you need to build a pipeline based on Azure Event Hub.
If you have Azure Functions and Web Apps - add Application Insights. According to my experience, I would suggest starting with a separate instance per each Azure Function resource or Service.
Create Alerts for each component separately. If you do it through UI - open component page at the portal and look for Alerts tab there. If you're automating the process (please do so as soon as possible), do not expect easy trip: I used ARM templates and terraform - in both cases, there are dozens of barely documented features.
Join related components core-metrics into Dashboards and share it with the team. This guide is a good starting point. Note, when you share the dashboard, it's also persisted as an azure resource in the subscription.
I have created a service plan to host web apps, but while creating I didn't keep an eye on the pricing details, so gave a standard pricing.
Now I want to reduce it to basic pricing, can I do it?
I can only see the pricing for it, but not able to change it.
Because I have changed the pricing tag for databases.
Thanks in Advance!!!!!
You could scale up your pricing tier under App Service---Settings.
For detailed information, such as VM sizes for each pricing tier, see App Service Pricing Details. For a table of service limits, quotas, and constraints, and supported features in each tier, see App Service limits.