Configure monitoring notifications for repository growth
Stay organized with collections
Save 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.
For more information about alerting policies, see
Alerting overview.
Before you begin
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 the
Monitoring Editor (roles/monitoring.editor) IAM role on your project.
For more information about granting roles, see Manage access to projects, folders, and organizations.
Ensure that you're familiar with the general concepts of alerting policies.
For information about these topics, see
Alerting 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, see
Create 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 is
Monitoring.
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.
From the Alerting page, select Create policy.
To select the resource, metric, and filters, expand the Select a metric menu and
then use the values in the New condition table:
Optional: To limit the menu to relevant entries, enter the resource or
metric name in the filter bar.
Select a Resource type. For example, select VM instance.
Select a Metric category. For example, select instance.
Select a Metric. For example, select CPU Utilization.
Select Apply.
Click Next and then configure the alerting policy trigger.
To complete these fields, use the values in the Configure alert trigger table.
Click Next.
Optional: To add notifications to your alerting policy, click
Notification channels. In the dialog, select one or more notification
channels from the menu, and then click OK.
To be notified when incidents are openend and closed, check
Notify on incident closure. By default, notifications are sent only when
incidents are openend.
Optional: Update the Incident autoclose duration. This field determines when
Monitoring closes incidents in the absence of metric data.
Optional: Click Documentation, and then add any information that you
want included in a notification message.
Click Alert name and enter a name for the alerting policy.
Click Create Policy.
New condition Field
Value
Resource and Metric
In the Resources menu, select Artifact Registry Repository.
In the Metric categories menu, select Repository.
In the Metrics menu, select Repository size.
To show all metric types, even those without data, click Active. By
default, the menus only show metric types with data. For more information,
see Metric not listed in menu.
Filter
Optional.
Use the resource_container label 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 to 500000000.
Retest window
The default value is No retest. With this setting, a single measurement can result in a
notification. For more information and an example, see
Alignment 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-03-06 UTC."],[[["This 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."],["Before creating an alerting policy, users need the Monitoring Editor IAM role, familiarity with alerting policy concepts, and configured notification channels."],["The process involves navigating to the Alerting page in the Google Cloud console, selecting \"Create policy,\" and configuring the resource, metric, filters, and alert trigger."],["Users 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."],["The 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 `Threshold` with the `Above Threshold` position."]]],[]]