To use Monitoring, you must have the appropriate
Identity and Access Management (IAM) permissions.
In general, each REST method in an API has an associated permission.
To use the method, or use a console feature that relies on the method, you must
have the permission to use the corresponding method.
Permissions aren't granted directly to users; permissions are instead granted
indirectly through roles, which group multiple permissions to make managing them
easier:
Roles for common combinations of permissions are predefined for you. However,
you can also create your own combinations of permissions by
creating IAM custom roles.
Predefined roles
This section lists a subset of IAM roles that are predefined by
Cloud Monitoring.
Name Title
Includes permissions
roles/monitoring.viewer
Monitoring Viewer
Grants read-only access to the Cloud Monitoring API.
roles/monitoring.editor
Monitoring Editor
Grants read-write access to the Cloud Monitoring API.
roles/monitoring.admin
Monitoring Admin
Grants full access to the Cloud Monitoring API.
The following role is used by service accounts for write-only access:
Write-only access to resource metadata. This provides exactly the permissions needed by the Ops Config Monitoring metadata agent and other systems that send metadata.
opsconfigmonitoring.resourceMetadata.write
Stackdriver Accounts Editor
(roles/stackdriver.accounts.editor)
Read/write access to manage Stackdriver account structure.
resourcemanager.projects.get
resourcemanager.projects.list
serviceusage.services.enable
serviceusage.services.get
stackdriver.projects.*
stackdriver.projects.edit
stackdriver.projects.get
Stackdriver Accounts Viewer
(roles/stackdriver.accounts.viewer)
Read-only access to get and list information about Stackdriver account structure.
resourcemanager.projects.get
resourcemanager.projects.list
stackdriver.projects.get
Stackdriver Resource Metadata Writer
Beta
(roles/stackdriver.resourceMetadata.writer)
Write-only access to resource metadata. This provides exactly the permissions needed by the Stackdriver metadata agent and other systems that send metadata.
stackdriver.resourceMetadata.write
Monitoring permissions included in Trusted Cloud by S3NS basic roles
The Monitoring permissions are the same as those
in roles/monitoring.viewer.
roles/editor
Editor
The Monitoring permissions are the same as those in
roles/monitoring.editor with the
exception of the stackdriver.projects.edit permission.
The role roles/editor doesn't include the
stackdriver.projects.edit permission.
roles/owner
Owner
The Monitoring permissions are the same as those in
roles/monitoring.admin.
Compute Engine access scopes
Access scopes are the legacy method of specifying permissions for your
Compute Engine VM instances. The following access scopes apply to
Monitoring:
Access scope
Permissions granted
https://www.googleapis.com/auth/monitoring.read
The same permissions as in roles/monitoring.viewer.
https://www.googleapis.com/auth/monitoring.write
The same permissions as in roles/monitoring.metricWriter.
Best practice. It is a good practice is to give your VM instances the
most powerful access scope (cloud-platform) and then use IAM
roles to restrict access to specific APIs and operations. For details, go to
Service account permissions.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-21 UTC."],[],[],null,[]]