.TH "GCLOUD_ALPHA_LOGGING_LOGS_DELETE" 1



.SH "NAME"
.HP
gcloud alpha logging logs delete \- delete all entries from a log in the global \f5_Default\fR log bucket



.SH "SYNOPSIS"
.HP
\f5gcloud alpha logging logs delete\fR \fILOG_NAME\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Delete all entries from a log in the global \f5_Default\fR log
bucket. With no entries, the log will not appear in the list of your project's
logs. However, you can write new entries to the log.



.SH "EXAMPLES"

To delete all entries from log 'my\-log' in the global \f5_Default\fR log
bucket:

.RS 2m
$ gcloud alpha logging logs delete my\-log
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fILOG_NAME\fR

Log name.


.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 "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. These variants are also available:

.RS 2m
$ gcloud logging logs delete
.RE

.RS 2m
$ gcloud beta logging logs delete
.RE