gcloud gemini logging-settings create

Stay organized with collections Save and categorize content based on your preferences.

gcloud gemini logging-settings create - create loggingSettings

gcloud gemini logging-settings create (LOGGING_SETTING : --location=LOCATION) [--labels=[LABELS,…]] [--log-metadata] [--log-prompts-and-responses] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG …]

LoggingSetting resource - Identifier. Name of the resource. Format:projects/{project}/locations/{location}/loggingsettings/{loggingsetting} The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

• provide the argument logging_setting on the command line with a fully specified name;
• provide the argument --project on the command line;
• set the property core/project.

This must be specified.

LOGGING_SETTING

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

To set the logging_setting attribute:

• provide the argument logging_setting on the command line.

This positional argument must be specified if any of the other arguments in this group are specified.

--location=LOCATION

The location id of the loggingSetting resource.

To set the location attribute:

• provide the argument logging_setting on the command line with a fully specified name;
• provide the argument --location on the command line.

--labels=[LABELS,…]

Labels as key value pairs.

KEY

Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers.

VALUE

Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers.

Shorthand Example:

--labels=string=string

JSON Example:

--labels='{"string": "string"}'

File Example:

--labels=path_to_file.(yaml|json)

--log-metadata

Whether to log metadata.

--log-prompts-and-responses

Whether to log prompts and responses.

--request-id=REQUEST_ID

An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request.

For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments.

The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).

Run $ gcloud help for details.