You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/platform/manage-cost-storage.md
+23-17Lines changed: 23 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.service: azure-monitor
11
11
ms.workload: na
12
12
ms.tgt_pltfrm: na
13
13
ms.topic: conceptual
14
-
ms.date: 04/26/2019
14
+
ms.date: 05/30/2019
15
15
ms.author: magoedte
16
16
ms.subservice:
17
17
---
@@ -146,29 +146,40 @@ Higher usage is caused by one, or both of:
146
146
147
147
## Understanding nodes sending data
148
148
149
-
To understand the number of computers (nodes) reporting data each day in the last month, use
149
+
To understand the number of computers reporting heartbeats each day in the last month, use
150
150
151
151
`Heartbeat | where TimeGenerated > startofday(ago(31d))
152
152
| summarize dcount(Computer) by bin(TimeGenerated, 1d)
153
153
| render timechart`
154
154
155
-
To get a list of computers sending **billed data types** (some data types are free), leverage the `_IsBillable`[property](log-standard-properties.md#_isbillable):
155
+
To get a list of computers which will be billed as nodes if the workspace is in the legacy Per Node pricing tier, look for nodes which are sending **billed data types** (some data types are free).
156
+
To do this, use the `_IsBillable`[property](log-standard-properties.md#_isbillable) and use the leftmost field of the fully qualified domain name. This returns the list of computers with billed data:
| summarize TotalVolumeBytes=sum(_BilledSize) by computerName`
162
163
163
-
Use these `union withsource = tt *` queries sparingly as scans across data types are expensive to execute. This query replaces the old way of querying per-computer information with the Usage data type.
164
+
The count of billable nodes seen can be estimated as:
164
165
165
-
This can be extended to return the count of computers per hour that are sending billed data types (which is how Log Analytics calculates billable nodes for the legacy Per Node pricing tier):
> Use these `union withsource = tt *` queries sparingly as scans across data types are expensive to execute. This query replaces the old way of querying per-computer information with the Usage data type.
174
+
175
+
A more accurate calculation of what will actually be billed is to get the count of computers per hour that are sending billed data types.
176
+
(For workspaces in the legacy Per Node pricing tier, Log Analytics calculates the number of nodes which need to be billed on an hourly basis.)
| summarize eventCount=count() by computerName | sort by count_ nulls last
213
219
```
214
220
215
221
If you want to see counts for billable data types are sending data to a specific computer, use:
@@ -394,4 +400,4 @@ When you receive an alert, use the steps in the following section to troubleshoo
394
400
- To configure an effective event collection policy, review [Azure Security Center filtering policy](../../security-center/security-center-enable-data-collection.md).
0 commit comments