https:\/\/www.microsoft.com\/en-gb\/industry\/blog\/cross-industry\/2019\/07\/18\/azure-log-analytics-looking-at-data-and-costs-part-3\/<\/a><\/p>\nYou would probably take the data projection (see post 3) and add it into Excel to do the math, but you can also use KQL for that.<\/p>\n
I assigned a price of $2.30 (line 1); most of the rest of the syntax is the same. This is correct as of 22\/7\/2019, please check and adjust. There are references to USD in the summarize command, if you do use a local currency there are two changes to make.<\/p>\n
\n\/\/ \n\/\/ How much would it cost if I added an extra nn Computers? \n\/\/ Only looks at the billable data \n\/\/ \n\/\/ You can add 2 options, \n\/\/ \n\/\/ 1. A count of the extra computers to add \n\/\/ 2. Count of days to look back at, to get historical data - suggested 31days \n\/\/ 3. USD $ price \n\/\/ All prices shown are in US Dollar ($). This is a summary estimate, not a quote. For up to date pricing information please visit https:\/\/azure.microsoft.com\/pricing\/calculator\/\t\t\t\t<\/code><\/p>\nlet aap = 2.30; \/\/Add Azure Pricing ($ USD) source: https:\/\/azure.microsoft.com\/en-us\/pricing\/details\/monitor\/ \nlet addExtraComputers=12; \nlet daystoSearch = 31d; \nunion withsource = tt * \n| where TimeGenerated > startofday(ago(daystoSearch)) \n| where _IsBillable == true \n| where isnotempty(Computer) \n| summarize \nComputerCount = dcount(Computer), \navgMbperComputer= round(sum(_BilledSize \/ (1024*1024)) \/ dcount(Computer),4), \nTotalGBytes = round(sum(_BilledSize \/ (1024*1024*1024)),4), \nCurrentCostUSD = round(sum(_BilledSize \/ (1024*1024*1024)) * aap,2), \nPredictedGB = round(sum(_BilledSize \/ (1024*1024*1024)) \/ dcount(Computer) * (dcount(Computer) + addExtraComputers),4), \nPredictedCostUSD= round(sum(_BilledSize \/ (1024*1024*1024)) \/ dcount(Computer) * (dcount(Computer) + addExtraComputers) * aap,2), \nAddedCompuerCnt = strcat(addExtraComputers,” added, new total= “, addExtraComputers + dcount(Computer))<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Building on Post 3 https:\/\/www.microsoft.com\/en-gb\/industry\/blog\/cross-industry\/2019\/07\/18\/azure-log-analytics-looking-at-data-and-costs-part-3\/ You would probably take the data projection (see post 3) and add it into Excel to do the math, but you can also use KQL for that. I assigned a price of $2.30 (line 1); most of the rest of the syntax is the same. This is correct as of<\/p>\n","protected":false},"author":424,"featured_media":17607,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","footnotes":""},"categories":[1],"post_tag":[128,424],"content-type":[],"coauthors":[],"class_list":["post-15480","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cross-industry","tag-azure","tag-hybridcloud"],"yoast_head":"\n
Azure Log Analytics: looking at data and costs \u2013 Part 4 - Microsoft Industry Blogs - United Kingdom<\/title>\n \n \n \n \n \n \n \n \n \n \n \n\t \n\t \n\t \n \n \n\t \n\t \n\t \n