.TH "GCLOUD_ALPHA_CONTAINER_FLEET_FLEETOBSERVABILITY_UPDATE" 1



.SH "NAME"
.HP
gcloud alpha container fleet fleetobservability update \- updates the Fleet Observability Feature resource



.SH "SYNOPSIS"
.HP
\f5gcloud alpha container fleet fleetobservability update\fR [\fB\-\-logging\-config\fR=\fILOGGING_CONFIG\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR This command updates the Fleet Observability Feature in a fleet.



.SH "EXAMPLES"

To describe the Fleet Observability Feature, run:

.RS 2m
$ gcloud alpha container fleet fleetobservability update \e
    \-\-logging\-config=LOGGING\-CONFIG
.RE



.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-logging\-config\fR=\fILOGGING_CONFIG\fR

Path of the YAML(or JSON) file that contains the logging configurations.

The JSON file is formatted as follows, with camelCase field naming:

.RS 2m
{
    "loggingConfig": {
        "defaultConfig": {
            "mode": "COPY"
        },
        "fleetScopeLogsConfig": {
            "mode": "MOVE"
        }
    }
}
.RE

The YAML file is formatted as follows, with camelCase field naming:

.RS 2m
\-\-\-
loggingConfig:
  defaultConfig:
    mode: COPY
  fleetScopeLogsConfig:
    mode: MOVE
.RE


.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 container fleet fleetobservability update
.RE

.RS 2m
$ gcloud beta container fleet fleetobservability update
.RE