HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/396/help/man/man1/gcloud_alpha_monitoring_channels_delete.1
.TH "GCLOUD_ALPHA_MONITORING_CHANNELS_DELETE" 1



.SH "NAME"
.HP
gcloud alpha monitoring channels delete \- delete a notification channel



.SH "SYNOPSIS"
.HP
\f5gcloud alpha monitoring channels delete\fR \fICHANNEL\fR [\fB\-\-force\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Delete a notification channel.


.SH "EXAMPLES"
The following command will delete channel
\f5projects/12345/notificationChannels/67890\fR, but only if the channel is not
actively referenced by existing alerting policies:

.RS 2m
$ gcloud alpha monitoring channels delete \e
    "projects/12345/notificationChannels/67890"
.RE

The following command will delete channel
\f5projects/12345/notificationChannels/67890\fR, even if the channel is still
actively referenced by alerting policies; if an existing policy references the
channel, it will be modified as a side\-effect to remove the channel.

.RS 2m
$ gcloud alpha monitoring channels delete \e
    "projects/12345/notificationChannels/67890" \-\-force
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Notification channel resource \- The notification channel to delete. This
represents a Cloud resource. (NOTE) Some attributes are not given arguments in
this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5channel\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fICHANNEL\fR

ID of the notification_channel or fully qualified identifier for the
notification_channel.

To set the \f5channel\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5channel\fR on the command line.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-force\fR

If true, the notification channel will be deleted regardless of its use in
alerting policies (the policies will be updated to remove the channel).


.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBmonitoring/v3\fR API. The full documentation for this
API can be found at: https://cloud.google.com/monitoring/api/



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist. This variant is also available:

.RS 2m
$ gcloud beta monitoring channels delete
.RE