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
Template for monitoring data reference article for Azure services. This article is support for the main "Monitor [servicename]" article for the service. -->
13
-
14
-
<!-- IMPORTANT STEP 1. Do a search and replace of [TODO-replace-with-service-name] with the name of your service. That will make the template easier to read -->
15
11
16
12
# Monitoring Azure Container Registry data reference
17
13
18
14
See [Monitor Azure Container Registry](monitor-service.md) for details on collecting and analyzing monitoring data for Azure Container Registry.
19
15
20
16
## Metrics
21
17
22
-
<!-- REQUIRED if you support Metrics. If you don't, keep the section but call that out. Some services are only onboarded to logs.
23
-
<!-- Please keep headings in this order -->
24
-
25
-
<!-- 2 options here depending on the level of extra content you have. -->
26
-
27
-
<!-- OPTION 1 - Minimum - Link to relevant bookmarks in https://docs.microsoft.com/azure/azure-monitor/platform/metrics-supported, which is auto generated from the metrics REST API. Not all metrics are published depending on whether your product group wants them to be. If the metric is published, but descriptions are wrong of missing, contact your PM and tell them to update them in the Azure Monitor "shoebox" manifest. If this article is missing metrics that you and the PM know are available, both of you contact azmondocs@microsoft.com.
28
-
-->
29
-
30
-
<!-- Example format. There should be AT LEAST one Resource Provider/Resource Type here.
31
-
32
-
This section lists all the automatically collected platform metrics collected for Azure Container Registry.
33
-
34
-
|Metric Type | Resource Provider / Type Namespace<br/> and link to individual metrics |
<!-- OPTION 2 - Link to the metrics as above, but work in extra information not found in the automated metric-supported reference article. NOTE: YOU WILL NOW HAVE TO MANUALLY MAINTAIN THIS SECTION to make sure it stays in sync with the metrics-supported link. For highly customized example, see [CosmosDB](https://docs.microsoft.com/azure/cosmos-db/monitor-cosmos-db-reference#metrics). They even regroup the metrics into usage type vs. resource provider and type.
42
-
-->
43
-
44
-
<!-- Example format.
45
-
46
-
Mimic the setup of metrics supported, but add extra information
47
-
Question: What is the granularity of the metrics - 1 min?
48
-
Question: Do we want to add quick usage blurbs?
49
-
50
-
-->
51
18
### Container Registry metrics
52
19
53
20
Resource Provider and Type: [Microsoft.ContainerRegistry/registries](/azure/azure-monitor/platform/metrics-supported#microsoftcontainerregistryregistries)
54
21
55
-
| Metric | Exportable via Diagnostic Settings? | Unit | Aggregation Type | Description | Dimensions | Usage |
| AgentPoolCPUTime | Yes | Seconds | Total | Total CPU time in seconds used by [ACR tasks](container-registry-tasks-overview.md) running on dedicated [agent pools](tasks-agent-pools.md)| None ||
58
-
| RunDuration | Yes | Milliseconds | Total | Total duration in milliseconds of [ACR tasks](container-registry-tasks-overview.md) runs | None ||
59
-
| StorageUsed | No | Bytes | Average | Storage used by the container registry: sum of capacity used by shared layers, manifest files, and replica copies in all repositories. | Geo-location ||
60
-
| SuccessfulPullCount | Yes | Count | Total | Number of successful pulls of container images and other artifacts from the registry | None ||
61
-
| SuccessfulPushCount | Yes | Count | Total | Number of successful pushes of container images and other artifacts to the registry | None ||
62
-
| TotalPullCount | Yes | Count | Total | Total number of pulls of container images and other artifacts from the registry | None ||
63
-
| TotalPushCount | Yes | Seconds | Total | Total number of pushes of container images and other artifacts to the registry | None ||
64
-
65
-
22
+
| Metric | Exportable via Diagnostic Settings? | Unit | Aggregation Type | Description | Dimensions |
| AgentPoolCPUTime | Yes | Seconds | Total | CPU time used by [ACR tasks](container-registry-tasks-overview.md) running on dedicated [agent pools](tasks-agent-pools.md)| None ||
25
+
| RunDuration | Yes | Milliseconds | Total | Duration of [ACR tasks](container-registry-tasks-overview.md) runs | None ||
26
+
| StorageUsed | No | Bytes | Average | Storage used by the container registry<br/><br/>Sum of storage for unique and shared layers, manifest files, and replica copies in all repositories<sup>1</sup> | Geo-location ||
27
+
| SuccessfulPullCount | Yes | Count | Total | Successful pulls of container images and other artifacts from the registry | None ||
28
+
| SuccessfulPushCount | Yes | Count | Total | Successful pushes of container images and other artifacts to the registry | None ||
29
+
| TotalPullCount | Yes | Count | Total | Total pulls of container images and other artifacts from the registry | None ||
30
+
| TotalPushCount | Yes | Seconds | Total | Total pushes of container images and other artifacts to the registry | None ||
66
31
67
-
<!-- Add additional explanation of reference information as needed here. Link to other articles such as your Monitor [servicename] article as appropriate. -->
32
+
<sup>1</sup>Because of layer sharing, registry storage used may be less than the sum of storage for individual repositories. When you [delete](container-registry-delete.md) a repository or tag, you recover only the storage used by manifest files and the unique layers referenced.
68
33
69
-
<!-- Keep this text as-is -->
70
34
For more information, see a list of [all platform metrics supported in Azure Monitor](https://docs.microsoft.com/azure/azure-monitor/platform/metrics-supported).
71
35
72
-
73
-
74
36
## Metric Dimensions
75
37
76
-
<!-- REQUIRED. Please keep headings in this order -->
77
-
<!-- If you have metrics with dimensions, outline it here. If you have no dimensions, say so.
78
-
Questions email azmondocs@microsoft.com -->
79
-
80
38
For more information on what metric dimensions are, see [Multi-dimensional metrics](/azure/azure-monitor/platform/data-platform-metrics#multi-dimensional-metrics).
81
39
82
-
<!--
83
-
[TODO-replace-with-service-name] does not have any metrics that contain dimensions.
84
-
85
-
*OR*
86
-
-->
87
40
Azure Container Registry has the following dimensions associated with its metrics.
88
41
89
-
<!-- See https://docs.microsoft.com/azure/storage/common/monitor-storage-reference#metrics-dimensions for an example. Part is copied below.
90
-
91
-
**--------------EXAMPLE format when you have dimensions------------------**
92
-
93
-
Azure Storage supports following dimensions for metrics in Azure Monitor. -->
94
-
95
42
| Dimension Name | Description |
96
43
| ------------------- | ----------------- |
97
44
|**Geo-location**| The Azure region for a registry or [geo-replica](container-registry-geo-replication.md). |
98
45
99
46
100
47
## Resource logs
101
-
<!-- REQUIRED. Please keep headings in this order -->
102
48
103
49
This section lists the types of resource logs you can collect for Azure Container Registry.
104
50
105
-
<!-- List all the resource log types you can have and what they are for -->
106
-
107
51
For reference, see a list of [all resource logs category types supported in Azure Monitor](/azure/azure-monitor/platform/resource-logs-schema).
108
52
109
-
110
-
111
-
<!-- OPTION 1 - Minimum - Link to relevant bookmarks in https://docs.microsoft.com/azure/azure-monitor/platform/resource-logs-categories, which is auto generated from the REST API. Not all resource log types metrics are published depending on whether your product group wants them to be. If the resource log is published, but category display names are wrong or missing, contact your PM and tell them to update them in the Azure Monitor "shoebox" manifest. If this article is missing resource logs that you and the PM know are available, both of you contact azmondocs@microsoft.com.
112
-
-->
113
-
114
-
<!-- Example format. There should be AT LEAST one Resource Provider/Resource Type here. -->
115
-
116
-
117
-
118
-
119
-
120
-
<!-- OPTION 2 - Link to the resource logs as above, but work in extra information not found in the automated metric-supported reference article. NOTE: YOU WILL NOW HAVE TO MANUALLY MAINTAIN THIS SECTION to make sure it stays in sync with the resource-log-categories link. You can group these sections however you want provided you include the proper links back to resource-log-categories article.
121
-
-->
122
-
123
-
<!-- Example format. Add extra information -->
124
-
125
53
### Container Registries
126
54
127
55
Resource Provider and Type: [Microsoft.ContainerRegistry/registries](/azure/azure-monitor/essentials/resource-logs-categories#microsoftcontainerregistryregistries)
128
56
129
57
| Category | Display Name | Details |
130
58
|:---------|:-------------|------------------|
131
59
| ContainerRegistryLoginEvents | Login Events | Registry authentication events and status, including the incoming identity and IP address |
132
-
| ContainerRegistryRepositoryEvents | Repository Events | Operations on images and other artifacts in registry repositories: push, pull, untag, delete (including repository delete), purge tag, and purge manifest |
60
+
| ContainerRegistryRepositoryEvents | Repository Events | Operations on images and other artifacts in registry repositories<br/><br/> The following operations are logged: push, pull, untag, delete (including repository delete), purge tag, and purge manifest |
133
61
|
134
62
135
63
## Azure Monitor Logs tables
136
-
<!-- REQUIRED. Please keep heading in this order -->
137
64
138
65
This section refers to all of the Azure Monitor Logs Kusto tables relevant to Azure Container Registry and available for query by Log Analytics.
<!-- OPTION 1 - Minimum - Link to relevant bookmarks in https://docs.microsoft.com/azure/azure-monitor/reference/tables/tables-resourcetype where your service tables are listed. These files are auto generated from the REST API. If this article is missing tables that you and the PM know are available, both of you contact azmondocs@microsoft.com.
144
-
-->
145
-
146
-
<!-- Example format. There should be AT LEAST one Resource Provider/Resource Type here.
<!-- OPTION 2 - List out your tables adding additional information on what each table is for. Individually link to each table using the table name. For example, link to [AzureMetrics](https://docs.microsoft.com/azure/azure-monitor/reference/tables/azuremetrics).
156
-
157
-
NOTE: YOU WILL NOW HAVE TO MANUALLY MAINTAIN THIS SECTION to make sure it stays in sync with the automatically generated list. You can group these sections however you want provided you include the proper links back to the proper tables.
158
-
-->
159
-
160
67
### Container Registry
161
68
162
69
| Table | Description |
163
70
|:---------|:-------------|
164
-
|[AzureActivity](/azure/azure-monitor/reference/tables/azureactivity)|<!-- description copied from previous link -->Entries from the Azure Activity log that provides insight into any subscription-level or management group level events that have occurred in Azure. |
165
-
|[AzureMetrics](/azure/azure-monitor/reference/tables/azuremetrics)|<!-- description copied from previous link -->Metric data emitted by Azure services that measure their health and performance. |
71
+
|[AzureActivity](/azure/azure-monitor/reference/tables/azureactivity)| Entries from the Azure Activity log that provides insight into any subscription-level or management group level events that have occurred in Azure. |
72
+
|[AzureMetrics](/azure/azure-monitor/reference/tables/azuremetrics)| Metric data emitted by Azure services that measure their health and performance. |
For a reference of all Azure Monitor Logs / Log Analytics tables, see the [Azure Monitor Log Table Reference](/azure/azure-monitor/reference/tables/tables-resourcetype).
171
77
172
-
173
-
To enable diagnostic settings for log collection, see [Collection and routing](monitor-service.md#collection-and-routing).
174
-
175
-
176
-
177
-
<!-- If your service uses the AzureDiagnostics table in Azure Monitor Logs / Log Analytics, list what fields you use and what they are for. Azure Diagnostics is over 500 columns wide with all services using the fields that are consistent across Azure Monitor and then adding extra ones just for themselves. If it uses service specific diagnostic table, refers to that table. If it uses both, put both types of information in. Most services in the future will have their own specific table. If you have questions, contact azmondocs@microsoft.com --
178
-
179
-
### Diagnostics tables
180
-
181
-
Q: Pretty sure this doesn't apply to ACR
182
-
-->
183
-
<!--
184
-
[TODO-replace-with-service-name] uses the [Azure Diagnostics](https://docs.microsoft.com/azure/azure-monitor/reference/tables/azurediagnostics) table and the [TODO whatever additional] table to store resource log information. The following columns are relevant.
185
-
186
-
**Azure Diagnostics**
187
-
188
-
| Property | Description |
189
-
|:--- |:---|
190
-
| | |
191
-
| | |
192
-
193
-
**[TODO Service-specific table]**
194
-
195
-
| Property | Description |
196
-
|:--- |:---|
197
-
| | |
198
-
| | |
199
-
200
-
-->
201
78
## Activity log
202
-
<!-- REQUIRED. Please keep heading in this order
203
-
Need PM input
204
-
-->
205
79
206
80
The following table lists the operations related to Azure Container Registry that may be created in the Activity log.
207
81
208
-
<!-- Fill in the table with the operations that can be created in the Activity log for the service. -->
209
82
| Operation | Description |
210
83
|:---|:---|
84
+
| TBD - what are some common entries that are useful to customers?||
211
85
|||
212
-
|||
213
-
214
-
<!-- NOTE: This information may be hard to find or not listed anywhere. Please ask your PM for at least an incomplete list of what type of messages could be written here. If you can't locate this, contact azmondocs@microsoft.com for help -->
215
86
216
87
## Schemas
217
-
<!-- REQUIRED. Please keep heading in this order -->
218
88
219
89
The following schemas are in use by Azure Container Registry's resource logs.
220
90
221
-
<!-- List the schema and their usage. This can be for resource logs, alerts, event hub formats, etc depending on what you think is important.
222
-
Q: How to get the schema descriptions added/improved.
223
-
-->
224
91
| Schema | Description |
225
92
|:--- |:---|
226
93
|[ContainerRegistryLoginEvents](/azure/azure-monitor/reference/tables/ContainerRegistryLoginEvents)| Schema for registry authentication events and status, including the incoming identity and IP address |
227
94
|[ContainerRegistryRepositoryEvents](/azure/azure-monitor/reference/tables/ContainerRegistryRepositoryEvents)| Schema for operations on images and other artifacts in registry repositories |
228
95
## See Also
229
96
230
-
<!-- replace below with the proper link to your main monitoring service article -->
231
97
- See [Monitor Azure Container Registry](monitor-service.md) for a description of monitoring an Azure container registry.
232
98
- See [Monitoring Azure resources with Azure Monitor](/azure/azure-monitor/insights/monitor-azure-resources) for details on monitoring Azure resources.
Copy file name to clipboardExpand all lines: articles/container-registry/monitor-service.md
+23-68Lines changed: 23 additions & 68 deletions
Original file line number
Diff line number
Diff line change
@@ -9,34 +9,17 @@ ms.service: container-registry
9
9
ms.date: 03/10/2021
10
10
---
11
11
12
-
<!-- VERSION 2
13
-
Template for the main monitoring article for Azure services. Keep the required sections and add/modify any content for any information specific to your service.
14
-
15
-
This article should be in the How-To Guides section of your TOC with the name *monitor-[TODO-replace-with-service-name].md* and the TOC title "Monitor [TODO-replace-with-service-name]". Keep the headings in this order.
16
-
17
-
Put accompanying reference information into an article in the Reference section of your TOC with the name *monitor-[service-name]-reference.md* and the TOC title "Monitoring data". -->
18
-
19
-
<!-- IMPORTANT STEP 1. Do a search and replace of [TODO-replace-with-service-name] with the name of your service. That will make the template easier to read -->
20
-
21
12
# Monitor Azure Container Registry
22
-
<!-- REQUIRED. Please keep headings in this order -->
23
-
<!-- Most services can use this section unchanged. Add to it if there are any unique charges if your service has significant monitoring beyond Azure Monitor. -->
24
13
25
14
When you have critical applications and business processes relying on Azure resources, you want to monitor those resources for their availability, performance, and operation. This article describes the monitoring data generated by Azure Container Registry and how you can use the features of Azure Monitor to analyze and alert on this data.
26
15
27
-
<!-- Optional diagram showing monitoring for your service. If you need help creating one, contact robb@microsoft.com -->
28
-
29
16
## Monitor overview
30
-
<!-- REQUIRED. Please keep headings in this order -->
31
-
<!-- Most services can use this section unchanged. Edit it if there are any unique charges if your service has significant monitoring beyond Azure Monitor. -->
32
17
33
18
The **Overview** page in the Azure portal for each registry includes a brief view of recent resource usage and activity, such as storage used and pull requests. This high-level information is useful, but only a small amount of the monitoring data is shown there.
<!-- REQUIRED. Please keep headings in this order -->
39
-
<!-- Most services can use this section unchanged. Edit it if there are any unique charges if your service has significant monitoring beyond Azure Monitor. -->
40
23
41
24
Azure Container Registry creates monitoring data using [Azure Monitor](/azure/azure-monitor/overview), which is a full stack monitoring service in Azure that provides a complete set of features to monitor your Azure resources in addition to resources in other clouds and on-premises.
42
25
@@ -50,80 +33,56 @@ Start with the article [Monitoring Azure resources with Azure Monitor](/azure/az
50
33
51
34
The following sections build on this article by describing the specific data gathered for Azure Container Registry and providing examples for configuring data collection and analyzing this data with Azure tools.
52
35
53
-
54
-
55
-
<!-- OPTIONAL SECTION. Only include if your service has and insight associated with it. Examples of insights include
- If you still aren't sure, contact azmondocs@microsoft.com.>
58
-
-
59
-
60
-
## Azure Monitor insights for Azure Container Registry
61
-
62
-
Some services in Azure have a special focused pre-built monitoring dashboard in the Azure portal that provides a starting point for monitoring your service. These special dashboards are called "insights".
63
-
64
-
<!-- Give a quick outline of what your "insight page" provides and refer to another article that gives details -->
65
-
66
-
67
-
68
-
69
36
## Monitoring data
70
37
71
-
<!-- REQUIRED. Please keep headings in this order -->
72
38
Azure Container Registry collects the same kinds of monitoring data as other Azure resources that are described in [Monitoring data from Azure resources](/azure/azure-monitor/insights/monitor-azure-resource#monitoring-data-from-Azure-resources).
73
39
74
40
See [Monitoring Azure Container Registry data reference](monitor-service-reference.md) for detailed information on the metrics and logs created by Azure Container Registry.
75
41
76
-
<!-- If your service has additional non-Azure Monitor monitoring data then outline and refer to that here. Also include that information in the data reference as appropriate. -->
77
-
78
42
## Collection and routing
79
43
80
-
<!-- REQUIRED. Please keep headings in this order -->
81
-
82
44
Platform metrics and the Activity log are collected and stored automatically, but can be routed to other locations by using a diagnostic setting.
83
45
84
46
Resource Logs are not collected and stored until you create a diagnostic setting and route them to one or more locations.
85
47
86
-
<!-- Include any additional information on collecting logs. The number of things that diagnostics settings control is expanding -->
87
-
88
48
See [Create diagnostic setting to collect platform logs and metrics in Azure](/azure/azure-monitor/platform/diagnostic-settings) for the detailed process for creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect. The categories for Azure Container Registry are listed in [Azure Container Registry monitoring data reference](monitor-service-reference.md#resource-logs).
89
49
90
50
> [!TIP]
91
51
> You can also create registry diagnostic settings by navigating to your registry in the portal. Then, select **Diagnostic settings** under **Monitoring**.
92
52
93
53
94
-
<!-- OPTIONAL: Add specific examples of configuration for this service. For example, CLI and PowerShell commands for creating diagnostic setting. Ideally, customers should set up a policy to automatically turn on collection for services. Azure monitor has Resource Manager template examples you can point to. See https://docs.microsoft.com/azure/azure-monitor/samples/resource-manager-diagnostic-settings. Contact azmondocs@microsoft.com if you have questions. -->
95
-
96
54
:::image type="content" source="media/monitor-service/diagnostic-settings.png" alt-text="Diagnostic settings for container registry":::
97
55
98
56
The metrics and logs you can collect are discussed in the following sections.
99
57
100
-
## Analyzing metrics
101
-
102
-
<!-- REQUIRED. Please keep headings in this order
103
-
If you don't support metrics, say so. Some services may be only onboarded to logs -->
58
+
## Analyzing metrics (preview)
104
59
105
60
You can analyze metrics for an Azure container registry with metrics from other Azure services using metrics explorer by opening **Metrics** from the **Azure Monitor** menu. See [Getting started with Azure Metrics Explorer](/azure/azure-monitor/platform/metrics-getting-started) for details on using this tool.
106
61
107
62
> [!TIP]
108
63
> You can also go to the metrics explorer by navigating to your registry in the portal. Then, select **Metrics (preview)** under **Monitoring**.
109
64
110
-
<!-- Point to the list of metrics available in your monitor-service-reference article. -->
111
65
For a list of the platform metrics collected for Azure Container Registry, see [Monitoring Azure Container Registry data reference metrics](monitor-service-reference.md#metrics)
112
66
113
67
For reference, you can see a list of [all resource metrics supported in Azure Monitor](/azure/azure-monitor/platform/metrics-supported).
114
68
69
+
### Azure CLI
70
+
71
+
The following Azure CLI commands can be used to get information about the Azure Container Registry metrics.
72
+
73
+
*[az acr show-usage](/cli/azure/acr/#az_acr_show_usage) - Get the storage used by an Azure container registry
74
+
*[az monitor metrics list-definitions](/cli/azure/monitor/metrics#az_monitor_metrics_list_definitions) - List metric definitions and dimensions
<!-- Optional: Call out additional information to help your customers. For example, you can include additional information here about how to use metrics explorer specifically for your service. Remember that the UI is subject to change quite often so you will need to maintain these screenshots yourself if you add them in. -->
121
83
122
84
## Analyzing logs
123
85
124
-
<!-- REQUIRED. Please keep headings in this order
125
-
If you don't support resource logs, say so. Some services may be only onboarded to metrics and the activity log. -->
126
-
127
86
Data in Azure Monitor Logs is stored in tables where each table has its own set of unique properties.
128
87
129
88
All resource logs in Azure Monitor have the same fields followed by service-specific fields. The common schema is outlined in [Azure Monitor resource log schema](/azure/azure-monitor/essentials/diagnostic-logs-schema#top-level-resource-logs-schema) The schema for Azure Container Registry resource logs is found in the [Azure Container Registry Data Reference](monitor-service-reference.md#schemas)
@@ -134,21 +93,23 @@ For a list of the types of resource logs collected for Azure Container Registry,
134
93
135
94
For a list of the tables used by Azure Monitor Logs and queryable by Log Analytics, see [Monitoring Azure Container Reference data reference](monitor-service-reference.md#azure-monitor-logs-tables)
136
95
137
-
<!-- Optional: Call out additional information to help your customers. For example, you can include additional information here about log usage or what logs are most important. Remember that the UI is subject to change quite often so you will need to maintain these screenshots yourself if you add them in. -->
138
-
139
96
### Sample Kusto queries
140
97
141
-
<!-- REQUIRED if you support logs. Please keep headings in this order -->
142
-
<!-- Add sample Log Analytics Kusto queries for your service. -->
143
-
144
98
> [!IMPORTANT]
145
99
> When you select **Logs** from the **Azure Container Registry** menu, Log Analytics is opened with the query scope set to the current registry. This means that log queries will only include data from that resource. If you want to run a query that includes data from other registries or data from other Azure services, select **Logs** from the **Azure Monitor** menu. See [Log query scope and time range in Azure Monitor Log Analytics](/azure/azure-monitor/log-query/scope/) for details.
146
100
147
-
<!-- REQUIRED: Include queries that are helpful for figuring out the health and state of your service. Ideally, use some of these queries in the alerts section. It's possible that some of your queries may be in the Log Analytics UI (sample or example queries). Check if so. -->
101
+
For example, the following query retrieves the most recent 24 hours of data from the **ContainerRegistryRepositoryEvents** table:
148
102
149
-
Following are queries that you can use to help you monitor your registry resource.
Following are queries that you can use to help you monitor your registry resource.
152
113
153
114
### Error events from the last hour
154
115
@@ -203,10 +164,6 @@ ContainerRegistryLoginEvents
203
164
204
165
## Alerts
205
166
206
-
<!-- SUGGESTED: Include useful alerts on metrics, logs, log conditions or activity log. Ask your PMs if you don't know.
207
-
This information is the BIGGEST request we get in Azure Monitor so do not avoid it long term. People don't know what to monitor for best results. Be prescriptive
208
-
-->
209
-
210
167
Azure Monitor alerts proactively notify you when important conditions are found in your monitoring data. They allow you to identify and address issues in your system before your customers notice them. You can set alerts on [metrics](/azure/azure-monitor/platform/alerts-metric-overview), [logs](/azure/azure-monitor/platform/alerts-unified-log), and the [activity log](/azure/azure-monitor/platform/activity-log-alerts). Different types of alerts have benefits and drawbacks.
211
168
212
169
@@ -223,7 +180,7 @@ The following table lists common and recommended alert rules for Azure Container
223
180
| metric | Signal: Storage used<br/>Operator: Greater than<br/>Aggregation type: Average<br/>Threshold value: 5 GB| Alerts if the registry storage used exceeds a specified value.|
224
181
||||
225
182
226
-
### Example: Send email alert when registry storage used exceeds a set value
183
+
### Example: Send email alert when registry storage used exceeds a value
227
184
228
185
1. In the Azure portal, navigate to your registry.
229
186
1. Select **Metrics (preview)** under **Monitoring**.
@@ -233,7 +190,7 @@ The following table lists common and recommended alert rules for Azure Container
233
190
1. In **Condition**, select **Add condition**.
234
191
1. In **Signal name**, select **Storage used**.
235
192
1. In **Chart period**, select **Over the last 24 hours**.
236
-
1. In **Alert logic**, in **Threshold value**, select **5**. In **Unit**, select **GB**.
193
+
1. In **Alert logic**, in **Threshold value**, select a value such as *5*. In **Unit**, select a value such as *GB*.
237
194
1. Accept default values for the remaining settings, and select **Done**.
@@ -243,7 +200,5 @@ The following table lists common and recommended alert rules for Azure Container
243
200
244
201
## Next steps
245
202
246
-
<!-- Add additional links. You can change the wording of these and add more if useful. -->
247
-
248
203
- See [Monitoring Azure Container Registry data reference](monitor-service-reference.md) for a reference of the metrics, logs, and other important values created by Azure Container Registry.
249
204
- See [Monitoring Azure resources with Azure Monitor](/azure/azure-monitor/insights/monitor-azure-resource) for details on monitoring Azure resources.
0 commit comments