Skip to content

Commit 39983d1

Browse files
committed
Blocking issues
1 parent 35d04a6 commit 39983d1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-functions/functions-consumption-costing.md renamed to articles/azure-functions/functions-consumption-costs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ The resulting chart contains the totals for both execution metrics in the chosen
9797

9898
As the number of execution units is so much greater than the execution count, the chart just shows execution units.
9999

100-
This chart shows a total of 1.11 billion `Function Execution Units` consumed in a two-hour period, measured in MB-milliseconds. To convert to GB-seconds, divide by 1,024,000. In this example, the function app consumed `1,110,000,000 / 1,024,000 = 1,083.98` GB-seconds. You can take this value and multiply by the current price of execution time on the [Functions pricing page][pricing page], which gives you the cost of these two hours, assuming you've already used any free grants of execution time.
100+
This chart shows a total of 1.11 billion `Function Execution Units` consumed in a two-hour period, measured in MB-milliseconds. To convert to GB-seconds, divide by 1024000. In this example, the function app consumed `1110000000 / 1024000 = 1083.98` GB-seconds. You can take this value and multiply by the current price of execution time on the [Functions pricing page][pricing page], which gives you the cost of these two hours, assuming you've already used any free grants of execution time.
101101

102102
### Azure CLI
103103

@@ -188,7 +188,7 @@ This command returns a JSON payload that looks like the following example:
188188
]
189189
}
190190
```
191-
This particular response shows that from `2019-09-11T21:46` to `2019-09-11T23:18`, during which the app consumed 1,110,000,000 MB-milliseconds (1,083.98 GB-seconds).
191+
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).
192192

193193
## Determine memory usage
194194

@@ -232,7 +232,7 @@ customMetrics
232232
| QueueTrigger MaxDurationMs | 90\.249 |
233233
| QueueTrigger MinDurationMs | 8\.522 |
234234

235-
## Next Steps
235+
## Next steps
236236

237237
> [!div class="nextstepaction"]
238238
> [Learn more about Monitoring function apps](functions-monitoring.md)

0 commit comments

Comments
 (0)