Skip to content

Commit 889c205

Browse files
Merge pull request #45399 from andresnava/patch-187
Update functions-consumption-costs.md
2 parents 296a089 + 8b02bbb commit 889c205

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-functions/functions-consumption-costs.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: conceptual
88

99
# Estimating Consumption plan costs
1010

11-
There are currently three types of hosting plans for an app that run in Azure Functions, with each plan having its own pricing model:
11+
There are currently three types of hosting plans for an app that runs in Azure Functions, with each plan having its own pricing model:
1212

1313
| Plan | Description |
1414
| ---- | ----------- |
@@ -81,11 +81,11 @@ Use [Azure Monitor metrics explorer](../azure-monitor/platform/metrics-getting-s
8181

8282
1. Select **Apply** to choose your function app as the resource to monitor.
8383

84-
1. From **Metric**, choose **Function execution count** and **Sum** for **Aggregation**. This adds the sum of the execution counts during chosen period to the chart.
84+
1. From **Metric**, choose **Function Execution Count** and **Sum** for **Aggregation**. This adds the sum of the execution counts during chosen period to the chart.
8585

8686
![Define a functions app metric to add to the chart](media/functions-consumption-costing/monitor-metrics-add-metric.png)
8787

88-
1. Select **Add metric** and repeat steps 2-4 to add **Function execution units** to the chart.
88+
1. Select **Add metric** and repeat steps 2-4 to add **Function Execution Units** to the chart.
8989

9090
The resulting chart contains the totals for both execution metrics in the chosen time range, which in this case is two hours.
9191

@@ -184,7 +184,7 @@ This command returns a JSON payload that looks like the following example:
184184
]
185185
}
186186
```
187-
This particular response shows that from `2019-09-11T21:46` to `2019-09-11T23:18`, during which the app consumed 1110000000 MB-milliseconds (1083.98 GB-seconds).
187+
This particular response shows that from `2019-09-11T21:46` to `2019-09-11T23:18`, the app consumed 1110000000 MB-milliseconds (1083.98 GB-seconds).
188188

189189
## Determine memory usage
190190

0 commit comments

Comments
 (0)