Configure monitoring notifications for repository growth
Stay organized with collectionsSave and categorize content based on your preferences.
This page describes how to create an alerting policy that can notify you when the
Artifact Registry repository growth exceeds a limit. These
instructions are for the Google Cloud console.
To get the permissions that
you need to create and modify alerting policies by using the Google Cloud console,
ask your administrator to grant you theMonitoring Editor(roles/monitoring.editor)
IAM role on your project.
For more information about granting roles, seeManage access to projects, folders, and organizations.
Ensure that you're familiar with the general concepts of alerting policies.
For information about these topics, seeAlerting overview.
Configure the notification channels that you want to use to receive any
notifications. For redundancy purposes, we recommend that you create
multiple types of notification channels. For more information, seeCreate and manage notification channels.
Create an alerting policy
To get notified when your Artifact Registry repository size grows beyond a specific size,
create an alerting policy. The alerting policy monitors the size of your repository and when that
size exceeds the threshold you specify, notifications are sent to all notification channels
attached to the alerting policy.
If you use the search bar to find this page, then select the result whose subheading isMonitoring.
If you haven't created your notification channels and if you want to be notified, then clickEdit Notification Channelsand add your notification channels. Return to theAlertingpage after you add your channels.
From theAlertingpage, selectCreate policy.
To select the resource, metric, and filters, expand theSelect a metricmenu and
then use the values in theNew conditiontable:
Optional: To limit the menu to relevant entries, enter the resource or
metric name in the filter bar.
Select aResource type. For example, selectVM instance.
Select aMetric category. For example, selectinstance.
Select aMetric. For example, selectCPU Utilization.
SelectApply.
ClickNextand then configure the alerting policy trigger.
To complete these fields, use the values in theConfigure alert triggertable.
ClickNext.
Optional: To add notifications to your alerting policy, clickNotification channels. In the dialog, select one or more notification
channels from the menu, and then clickOK.
To be notified when incidents are openend and closed, checkNotify on incident closure. By default, notifications are sent only when
incidents are openend.
Optional: Update theIncident autoclose duration. This field determines when
Monitoring closes incidents in the absence of metric data.
Optional: ClickDocumentation, and then add any information that you
want included in a notification message.
ClickAlert nameand enter a name for the alerting policy.
ClickCreate Policy.
New condition Field
Value
Resource and Metric
In theResourcesmenu, selectArtifact Registry Repository. In theMetric categoriesmenu, selectRepository. In theMetricsmenu, selectRepository size.
To show all metric types, even those without data, clickActive. By
default, the menus only show metric types with data. For more information,
seeMetric not listed in menu.
Filter
Optional.
Use theresource_containerlabel to alert for a project or
organization by entering the project ID or organization ID.
Set to the size of the repository in bytes that triggers the alert. For example, to trigger an
alert if repository size grows larger than 0.5GB, set the threshold value to500000000.
Retest window
The default value isNo retest. With this setting, a single measurement can result in a
notification. For more information and an example, seeAlignment period and duration settings.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThis page provides instructions on creating an alerting policy in the Google Cloud console to monitor Artifact Registry repository growth and send notifications when a specified size threshold is exceeded.\u003c/p\u003e\n"],["\u003cp\u003eBefore creating an alerting policy, users need the Monitoring Editor IAM role, familiarity with alerting policy concepts, and configured notification channels.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves navigating to the Alerting page in the Google Cloud console, selecting "Create policy," and configuring the resource, metric, filters, and alert trigger.\u003c/p\u003e\n"],["\u003cp\u003eUsers can customize the alerting policy by adding notification channels, defining incident autoclose duration, adding documentation, and setting a specific threshold value to trigger alerts based on repository size.\u003c/p\u003e\n"],["\u003cp\u003eThe necessary configuration for monitoring the repository size is setting the Resource as Artifact Registry Repository, the Metric Category as Repository, the Metric as Repository size and setting the condition type to \u003ccode\u003eThreshold\u003c/code\u003e with the \u003ccode\u003eAbove Threshold\u003c/code\u003e position.\u003c/p\u003e\n"]]],[],null,["# Configure monitoring notifications for repository growth\n\nThis page describes how to create an alerting policy that can notify you when the\nArtifact Registry repository growth exceeds a limit. These\ninstructions are for the Google Cloud console.\n\nFor more information about alerting policies, see\n[Alerting overview](/monitoring/alerts).\n\nBefore you begin\n----------------\n\n1.\n\n To get the permissions that\n you need to create and modify alerting policies by using the Google Cloud console,\n\n ask your administrator to grant you the\n\n\n [Monitoring Editor](/iam/docs/roles-permissions/monitoring#monitoring.editor) (`roles/monitoring.editor`)\n IAM role on your project.\n\n\n For more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\n You might also be able to get\n the required permissions through [custom\n roles](/iam/docs/creating-custom-roles) or other [predefined\n roles](/iam/docs/roles-overview#predefined).\n\n For more information about Cloud Monitoring roles,\n see [Control access with Identity and Access Management](/monitoring/access-control).\n2. Ensure that you're familiar with the general concepts of alerting policies.\n For information about these topics, see\n [Alerting overview](/monitoring/alerts).\n\n3. Configure the notification channels that you want to use to receive any\n notifications. For redundancy purposes, we recommend that you create\n multiple types of notification channels. For more information, see\n [Create and manage notification channels](/monitoring/support/notification-options).\n\nCreate an alerting policy\n-------------------------\n\nTo get notified when your Artifact Registry repository size grows beyond a specific size,\ncreate an alerting policy. The alerting policy monitors the size of your repository and when that\nsize exceeds the threshold you specify, notifications are sent to all notification channels\nattached to the alerting policy.\n\n#### Steps to create an [alerting policy](/monitoring/alerts/using-alerting-ui#create-policy).\n\nTo create an alerting policy, do the following:\n\n1. In the Google Cloud console, go to the\n *notifications* **Alerting** page:\n\n [Go to **Alerting**](https://console.cloud.google.com/monitoring/alerting)\n\n \u003cbr /\u003e\n\n If you use the search bar to find this page, then select the result whose subheading is\n **Monitoring**.\n2. If you haven't created your notification channels and if you want to be notified, then click **Edit Notification Channels** and add your notification channels. Return to the **Alerting** page after you add your channels.\n3. From the **Alerting** page, select **Create policy**.\n4. To select the resource, metric, and filters, expand the **Select a metric** menu and then use the values in the **New condition** table:\n 1. Optional: To limit the menu to relevant entries, enter the resource or metric name in the filter bar.\n 2. Select a **Resource type** . For example, select **VM instance**.\n 3. Select a **Metric category** . For example, select **instance**.\n 4. Select a **Metric** . For example, select **CPU Utilization**.\n 5. Select **Apply**.\n5. Click **Next** and then configure the alerting policy trigger. To complete these fields, use the values in the **Configure alert trigger** table.\n6. Click **Next**.\n7. Optional: To add notifications to your alerting policy, click\n **Notification channels** . In the dialog, select one or more notification\n channels from the menu, and then click **OK**.\n\n To be notified when incidents are openend and closed, check\n **Notify on incident closure**. By default, notifications are sent only when\n incidents are openend.\n8. Optional: Update the **Incident autoclose duration**. This field determines when Monitoring closes incidents in the absence of metric data.\n9. Optional: Click **Documentation**, and then add any information that you want included in a notification message.\n10. Click **Alert name** and enter a name for the alerting policy.\n11. Click **Create Policy**.\n\nWhat's next\n-----------\n\n- To learn more about metric-threshold alerting policies, see [Create metric-threshold alerting policies](/monitoring/alerts/using-alerting-ui).\n- To view available Artifact Registry metrics, see [Google Cloud metrics](/monitoring/api/metrics_gcp_a_b#gcp-artifactregistry)"]]
