Add a cost calculator or explain usage stats easier for purchasing
There are a few people wondering about how we can estimate usage and how that usage is calculated. See here
The new Usage page provides information on actual usage and can be used to estimate what is needed for purchases.
The included views will give you information on:
• How much data is sent to Log Analytics and by which Computers
• How much data is sent for each solution
• How much data isn’t associated with a computer
• Which computers are sending data and which computers haven’t recently sent data
• How many nodes are sending data for each of the OMS offers (Insight & Analytics, Automation & Control, and Security and Compliance)
• How long it takes for Log Analytics to make data searchable
There is also a calculator available here:
Tomas Lugn commented
I would like to see that you could tag the machins and separat the cost by tag.
I would also like to see the cost and usage data per computer.
I would also like to be able to export the cost and usage data to Excel. For example cost per computer.
Dirk Ringe commented
Please show the usage per solution not only on a monthly basis but also on a daily basis. When I evaluate a new solution it is nearly impossible to forecast the impact on costs unless the solution has run a month (or close to it)
I think the page has a fair amount of information today. If I must think of improvements, I would add:
drill down on costs for SP
drill down on costs for Computer
set a cap limit or a notification when a certain cap limit is surpassed
How do you like the newer blade that shows SLA information next to 'Usage' ? What else are we missing in this space?
Basically the estimator says "if you were on standard or premium, in the last 30 days you would have spent so much".
The usage page shows 30 days.
The new 'estimated' cost is calculated based on the last 30 days of data, all it does is multiplying your total usage in the last 30 days by the corresponding rate/price plan.
Add the billing period for the estimate to the current implementation. It's not clear to me the period of time the estimates refres to. (I guess it's a monthly fee)
It's not clear to which time period the estimated cost applies. I guess it applies to a monthly cycle, but the UI is not clear.
The GBs get metered when received, and that drives billing. You only get billed for NEW data coming into the system. They don't get billed over and over again for OLD data already in the system.
So if you plan to keep your data for a year, you pick premium, and if you send 1GB per day, you get billed for 1GB on that day and you can query it for a year if you stay on premium plan, even if you don't send any new data anymore.
We will consider a 'forecast'-type tool / calculator if there is enough demand, of course.
It is not immediately prioritized anyhow.
Looking at the 'Servers and Usage' page should give you a good idea of the volume sizes: the 'assessment' type IP's (SQL Assessment, Update Assessment, Malware Assessment) typically produce little data and predictably (i.e. daily, weekly, etc).
Performance Data for Capacity management is quite a bit of data, but if the number of hosts/VMs doesn't peak all of a sudden, its daily produce of performance counter is largely constant to observe.
Log Management, with certain Event Logs and IIS logs can be collecting tons of data - but it's configurable, so you regulate the knob - and you can watch it.
Windows Events anyhow (and traffic to a web site) can still be fairly unpredictable and have 'bursts' - more errors on a certain day, or you are under attack, or you get more customers visiting your site... whatever the reason, logs are more variable in nature/volume and have a higher velocity. You need to observe your own collection policy and what your environment produces in the first place.
Ultimately, you can set a spending limit/cap on your azure subscription and configure alerting in azure account billing page (this is another azure preview feature that works across services and warns you if your bill is trending too much up - you configure when).